← ClaudeAtlas

staged-coding-9-verifylisted

staged-coding stage 9 - refuse to lie. Builds the claim table (every claim this run made, how it was mechanically checked, disposition verified/failed/unsupported/unverifiable), audits plan completion, grades the CARD against the code in both directions, and checks the gate is not stale. Signs its ledger line on finish. Triggers: /staged-coding-9-verify, or invoked in order by /staged-coding.
Shadysmetools/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Shadysmetools/claude-skills
# Stage 9 - refuse to lie Part of the `/staged-coding` chain. Runs after stage 8.5 (design match) and before stage 9.5 (the refuter). The conductor carries the cross-cutting rules; read them there. ## Inputs - Every claim made across this run: stage evidence lines, numbers, file references, behaviour claims, citations - Stage 8's evidence (what you clicked, what you saw, the screenshots). That is this stage's proof, not a fresh one - The gate sha from stage 6, to check staleness - The ticket card's own text ## What to do Do not claim done; prove it. Run a verification-before-completion skill if available. The evidence from stage 8 is the proof and goes in the PR body. ### (a) The claim table Extract EVERY claim this run has made (numbers like "fixed 7 rows", file references, behaviour like "the server now returns 400", citations) and give each a row: | claim | mechanical check (grep count, file exists, query, re-run test) | disposition | |---|---|---| Dispositions are exactly **`verified` / `failed` / `unsupported` / `unverifiable`**. - Any `failed` -> back to stage 4. - Any `unsupported` claim is DELETED from the PR body and the card. An unbacked number does not ship; it dies here. - `unverifiable` stays, labelled as such, with the reason. ### (b) Plan-completion audit Every plan item / slice criterion gets DONE / PARTIAL / NOT_DONE / CHANGED / UNVERIFIABLE. A concrete file path must resolve to DONE or NOT_DONE by checking it exists, never UNVERIFIABLE. Be c