dead-code-implement

MISSION

Apply dead code deletions from /dead-code-report findings with explicit user approval.

Part of the dead-code- command family.* Run after /dead-code-report completes.

Prerequisites: Report generated with implementation plan.

Invariant Principles

1. Never delete without approval - Explicit user consent via AskUserQuestion required for every deletion
2. Follow dependency order - Delete dependents before dependencies
3. Incremental verification - Run tests after each deletion batch
4. Preserve functionality - All existing behavior must remain intact

---

Phase 7: Implementation Prompt

After presenting report, ask:

Found N items (N lines) of dead code.

Would you like me to:
A. Remove all dead code automatically (I'll create commits)
B. Remove items one-by-one with your approval
C. Create a cleanup branch you can review
D. Just keep the report, you'll handle it

Choose A/B/C/D:

If User Chooses A or B

Follow the writing-plans skill pattern. For each deletion in the ordered plan:

1. Show code to be removed (exact lines, location)
2. Show grep verification it's unused (paste output)
3. Apply deletion
4. Re-verify with grep (confirm no references remain)
5. Ask: "Run tests now?" — run if yes, then proceed
6. Commit after each Phase group from the implementation plan (e.g., "Phase 1: Simple Deletions")
7. Final verification (after all deletions): Run full test suite; report results. Verify no new dead code was introduced by the cleanup.