Inspiration
Specs in Jira and Confluence are often ambiguous, so teams argue about what "done" means after the work is already built. SignOff turns those specs into a shared, checkable definition of done.
What it does
SignOff turns Jira/Confluence specs into structured acceptance criteria + test plans in a Jira panel, and exposes the same criteria via Atlassian MCP so external coding agents verify against the ground truth — with evidence — back into Jira.
Open any Jira issue with a spec in its description and use the SignOff panel buttons in order 1→4: generate acceptance criteria, generate a test plan, verify criteria with evidence, and see the verdict. Evidence-less verified/failed reports are rejected in code, so a claim without proof cannot pass.
How we built it
Built with Atlassian Forge (jira:issuePanel, actions, rovo:mcp), Node.js, deterministic parser (no required LLM), optional Gemini enrichment, Jira issue entity properties as the shared ground-truth store.
Ground truth is stored as Jira issue entity properties — not Forge hosted storage, which is partitioned per product installation — so reports filed over MCP are immediately visible in the Jira panel.
MCP
The app declares a rovo:mcp module exposing three tools backed by the same action pipeline as the panel: get_acceptance_criteria (structured criteria for an issue), get_test_plan (the generated checklist), report_verification (per-criterion status + mandatory evidence; evidence-less verified/failed reports are rejected in code). A site admin enables exposure per installation (Atlassian Administration → Apps → Sites → Connected apps → "Expose tools to MCP-compatible apps"); tools then live at https://mcp.atlassian.com/forge/54e2a522-51a3-45f4-8c6f-d692e81c8405 and authenticate per user via OAuth. MCP-invoked functions call product APIs as the app (asApp), and because ground truth is stored as Jira issue entity properties — not Forge hosted storage, which is partitioned per product installation — reports filed over MCP are immediately visible in the Jira panel. Verified end-to-end on a Free site: tools/list = 3 tools, get_acceptance_criteria SCRUM-5 = 8 criteria, report_verification accepted with evidence and rejected without.
Testing instructions
Install from its Atlassian Marketplace listing (https://marketplace.atlassian.com/apps/421616191), open any Jira issue with a spec in its description, use the SignOff panel buttons in order 1→4. No configuration or API key is required; the optional Gemini enrichment is off by default and not needed to evaluate the app. Demo site: https://signoff-dev.atlassian.net (issue SCRUM-5 shows the staged state: 8 criteria, 6/8 verified, verdict FAIL, gap issue SCRUM-9, test plan SCRUM-7). For MCP: enable the endpoint in Connected apps, point any MCP client at the endpoint URL above, sign in with OAuth, and call get_acceptance_criteria on SCRUM-5.
Marketplace
Marketplace listing: https://marketplace.atlassian.com/apps/421616191 (submitted, pending approval). Review ticket: https://ecosystem.atlassian.net/browse/ECOHELP-186449
Challenges we ran into
Keeping one ground truth across the Jira panel and MCP, enforcing evidence for verification, and making the deterministic parser useful without requiring an LLM or API key.
Built With
- atlassian-forge
- atlassian-mcp
- confluence
- gemini
- jira
- node.js