AI agents finish Jira issues. Proof of Done makes them prove it.

Coding agents say “done, tested” whether or not they ran a single test. Proof of Done is a Forge app for Jira that refuses a hand-in until the agent shows where to look, how to check, what evidence backs it and how every acceptance criterion is met. A human accepts or returns the work from the issue in one click.

The loop

1. Claim. An agent (Claude Code, Cursor, any MCP client) lists agent-ready issues and claims one under a stable name.
2. Gate. “Done, tested” is refused before anything is written: no https link, fewer than two steps, no checkable evidence, a criterion left out.
3. Evidence. Screenshots and logs are uploaded to the issue after the claim — older evidence does not count.
4. Review. The Rovo agent “Proof of Done Reviewer” reads the criteria, the evidence and the cited logs and recommends accept or return.
5. Decide. The issue’s reporter or a project admin clicks Accept or Return in the issue panel. Accepted work moves to Done.

Every claim, refusal, hand-in, review and decision is written to an append-only, hash-chained ledger. The Agent Trust Board shows, per agent, how much of its work was accepted on the first look — so a team knows which agents to trust with what.

What is inside

• Atlassian MCP tools (rovo:mcp): pod-list-tasks, pod-get-task, pod-claim-task, pod-attach-evidence, pod-submit-proof.
• Rovo agent “Proof of Done Reviewer” with actions to read the review package, record findings and show the trust board.
• Issue panel with the hand-in, the evidence and the Accept / Return buttons; Agent Trust Board as a Jira page.
• skill.md — open instructions any agent can load to work with the app correctly the first time.

Runs on Atlassian: the app has no external calls. Everything it stores stays in Forge storage of your site.

Install and try it

1. Open the installation link from the submission, choose your Jira Cloud site and approve.
2. Admin: Atlassian Administration → Apps → Connected apps → Proof of Done → Tools → enable, so external agents can connect.
3. Connect an agent: claude mcp add --transport http proof-of-done https://mcp.atlassian.com/forge/e4c3eca7-a345-43aa-bcf0-ecb1543bd4be, then /mcp to sign in.
4. Label an issue agent-ready and write acceptance criteria in its description as a numbered list (AC1: …, AC2: …).
5. Ask the agent to take the issue. Watch the Proof of Done panel on the issue; accept or return the work there.

Support

Write to hi@ihor.work. We answer within two business days.