← ClaudeAtlas

retiring-a-finished-planlisted

Use when the work in an implementation plan or design spec is complete, when a feature ships and its planning document is still in the tree, or after a plan's branch merges.
rgant/claude-plugins · ★ 0 · Data & Documents · score 72
Install: claude install-skill rgant/claude-plugins
# Retiring a Finished Plan ## Overview The plan is done. Its job is over. **Core principle: keep only what the code cannot say.** Run this at the end of the work, before the plan ages into the backlog. If a backlog has already built up, use the `writing:auditing-doc-backlogs` skill instead. ## The Rule ``` PROPOSE THE DELETE. DELETE ONLY AFTER THE USER CONFIRMS. ``` You never stage and never commit. The user reviews the working tree and signs the commit. ## Why the plan must go, not stay A shipped plan reads as current. It names functions that never got written under those names and describes routes the work replaced. A superpowers plan also carries `REQUIRED SUB-SKILL: use subagent-driven-development to implement this plan`. That line is a standing instruction to a future agent to rebuild work that already shipped. `git log` holds the plan. The working tree is for what is true now. ## Step 0 — Learn where a living document lives Read the repository's own instruction file (`CLAUDE.md`, `AGENTS.md`, `CONTRIBUTING.md`) for a rule about where a document goes. Name the living documents this project already uses: a `README.md`, an architecture document, a status document, an operator runbook. Every destination below must be one this step found. **Never introduce a document type the repository does not already use.** A convention from a neighboring project is not evidence for this one. ## Step 1 — Confirm the work shipped Name one function, route, table, or flag the