plan-cleanup

# /plan-cleanup Remove planning artifacts and tech debt after a plan has been executed. No new work. No scope additions. Just cleanup. > **Structured execution spec:** [`protocol.yon`](protocol.yon). Read it for the canonical rules and step sequence; this file is explanation. The two must stay in sync — if you edit one, update the other and refresh the `@STAMP` date. ## Phase 1 — Identify Artifacts Scan for artifacts left behind by the planning and execution cycle: **Planning docs** (created by `/plan-create`, `/plan-phases`, `/plan-deep-dive`): - `PLAN.md` - `implementation_plan.md` - `task.md` (if created as a plan artifact, not a pre-existing project file) - Any `*-plan.md` files in the project root **Execution scaffolding** (created by `/plan-execute` or setup steps): - Temp files, stub files, or files explicitly marked as temporary in the plan - Any file whose sole purpose was to scaffold or support the plan run **Tool artifacts:** - `.claude/` directories created incidentally in skill or tool folders (not the user's project `.claude/`) For each candidate, verify: **is this file needed by the project going forward?** If yes, leave it. If it exists only because of the planning cycle, it's an artifact. **Gate:** list every artifact found before removing anything. If none found, declare "No artifacts found — workspace is clean" and stop. ## Phase 2 — Confirm and Remove Present the artifact list to the user: > "Found the following planning artifacts: > - [file...