← ClaudeAtlas

staged-coding-10-landlisted

staged-coding stage 10 - land. Get the owner's OK on the local proof, open the PR with the signed ledger, merge to staging, prove it live, publish the proof and update the card, then OPEN (never merge) the production PR and stop. Signs its ledger line twice. Triggers: /staged-coding-10-land, or invoked in order by /staged-coding.
Shadysmetools/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Shadysmetools/claude-skills
# Stage 10 - land it, merge it, prove it live, report it, open the door to production Part of the `/staged-coding` chain. Runs last, after stage 9.5's refuter survives. The conductor `/staged-coding` carries the cross-cutting rules; read them there. Settings come from `.staged-coding.json` (`config.<key>`). ## Inputs - The surviving refuter verdict from stage 9.5 (a killed claim never reaches this stage) - The ledger file with every prior stage signed (the one path resolved at stage 0) - Evidence: the stage-6 gate findings, the stage-8 browser-proof screenshots - The ticket id (or every slice id, for an epic) and the working branch ## Before anything: the ledger must be complete ``` python <staged-coding skill dir>/scripts/sign.py check --ledger <ledger path> ``` Exit 3 lists every unsigned stage (and any checkpoint signed by the builder's own model). An unsigned stage means the pipeline is not done, whatever the code looks like. Stage 10 is excluded by default because it signs right before the PR opens. Always pass the same `--ledger` path every stage used; a different path reports every stage MISSING. Then `sign.py render --ledger <ledger path>` prints the STAGE LEDGER block. Read its tail: `gate sha <sha> . N commits since` - N>0 means code changed after the stage-6 gate ran. Go back and re-run stage 6 first. ## What to do The builder owns the whole loop: PR, merge to staging, card, live proof, report, production PR. "A PR exists" is not done; a pile of correct, u