Menu
Verify implementation against the plan, update living documentation, and close out the change.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Execute an approved implementation plan task by task — verify each step fresh, stop when blocked, and ask instead of guessing.
You MUST use this before any implementation. Clarify intent, shape the design, and get approval before touching code.
Create an implementation plan for an approved design with exact file paths, ordered tasks, concrete verification, and no placeholders.
Systematic debugging protocol — find the root cause before proposing fixes.
Check for available upgrades to the pi coding agent framework by comparing the current `@earendil-works/pi-*` or legacy `@mariozechner/pi-*` version in package.json against releases on `earendil-works/pi`. Use this skill whenever the user asks to upgrade pi, update pi, check pi changelogs/releases, or migrate off the deprecated `@mariozechner/*` packages.
| name | supi-flow-archive |
| description | Verify implementation against the plan, update living documentation, and close out the change. |
| disable-model-invocation | true |
Use after /skill:supi-flow-apply when implementation is complete. This is a docs-first verification closeout, not a repository cleanup.
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE. Run the proof fresh, read the result, check the exit status.
Read the ticket metadata and content, then list its tasks. Archive only runs when a ticket exists — trivial flows close out in conversation. If unclear, ask which change to archive.
For every planned task, run fresh verification:
Stop if: a task is incomplete and unexplained, tests weren't run fresh, the result diverges from approved intent, or claimed manual verification wasn't actually performed.
git diff for the real delta.Close the ticket — requires nonblank verification evidence and all tasks complete. Stores the evidence in the ticket archive.
If only ticket files changed: commit with chore(tndm): close <ticket_id>. Otherwise ask whether to commit now (use the commit skill if available) or let the user handle it manually.
Stop if you're treating this as repository cleanup instead of a verification closeout.