← ClaudeAtlas

staged-coding-8-provelisted

staged-coding stage 8 - PROVE IT (the loop). Runs the real feature locally in a logged-in browser, proves a before/after pair where the BEFORE fails, checks live data actually changed, and judges honestly. Fails back to stage 4, capped at config.max_prove_rounds. Signs its ledger line on finish. Triggers: /staged-coding-8-prove, or invoked in order by /staged-coding.
Shadysmetools/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill Shadysmetools/claude-skills
# Stage 8 - PROVE IT (the loop) Part of the `/staged-coding` chain. Runs after stage 7 (logged-in browser) and before stage 8.5 (design match). The conductor carries the cross-cutting rules (unit of work = the whole epic, lane, which model builds vs checks, the ledger law, stop conditions); read them there. This stage proves the feature WORKS. Stage 8.5 proves it LOOKS RIGHT. ## Inputs - A logged-in automation browser session (stage 7's output) - The ticket's acceptance criteria (EPIC lane) or the defect's reproduction (BUG lane), and whether the change writes anything (decides whether the live-data check is mandatory) - Whether the change alters an EXISTING screen (before/after proof) or adds a new one ## Choose the rig by what your diff touched - **Anything under `config.server_dirs`** -> run BOTH halves locally (`config.local_start`, served at `config.local_url`), so the request under test actually executes your server code. A local client proxied to a deployed backend does not contain your change: a server diff "proved" that way is not proved at all. - **Client-only diff** (only `config.frontend_dirs`) -> a local client against `config.staging_url` is acceptable and cheaper. - Name the choice in your ledger evidence line. Rules while the local stack runs: - **Never run a database migration from a laptop** if local points at a shared database. Migrations reach shared environments only when a PR merges. - **Keep outbound side effects disarmed** (email, ch