← ClaudeAtlas

record-evidencelisted

Use after implementing a Dispatch ticket and running its checks, to produce and record acceptance-criterion evidence, then STOP. Invoke whenever you have finished and committed work on your claimed ticket and need to evidence each AC. Recording evidence is where your job ENDS — the runner (not you) records the delivery, pushes/opens the PR, and submits for review.
tmj-90/gaffer · ★ 0 · Code & Development · score 69
Install: claude install-skill tmj-90/gaffer
# Record acceptance-criterion evidence The runner claimed this ticket for you and holds the claim. This skill has one job: evidence every acceptance criterion with real, true proof — and then **stop**. You do NOT submit, push, or open a PR: once your ACs are evidenced, the runner runs the gates, records the delivery, pushes/opens the PR, and submits for review. ## Steps 1. **Re-read the acceptance criteria.** Call `get_ticket` (Dispatch MCP) for the claimed ticket and list each AC with its current status. 2. **For every AC, produce real evidence.** Prefer machine-checkable proof over prose: - tests: the exact command you ran and its passing summary → `evidence_type: test_output` - coverage: the coverage delta → `coverage_report` - the change itself: the branch name and a one-paragraph diff summary → `diff_summary` - anything else verifiable (a log, a screenshot path) with the matching type 3. **Record each one** with `record_ac_evidence` (Dispatch MCP), passing the `ticket_id`, the `ac_id`, the `evidence_type`, and a concise `summary`. You do NOT need to pass a `claim_token` — the runner holds the claim and injects the token into your tools automatically. One evidence row per AC minimum; recording AC evidence marks that AC satisfied. 4. **Once every AC is evidenced, you are done — STOP.** Do **not** submit for review, push, or open a PR. The runner runs the gates, records the delivery, pushes/opens the PR, and submits for review. There is n