Menu
Archive a completed implementation plan. Moves the plan to archive/ and updates its status to COMPLETE.
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
Draft or amend an Architecture Decision Record (ADR) from a research synthesis or a design decision. Use when a decision needs to become a durable, reviewable record — and when extending or correcting a decision that has already landed.
Review an Architecture Decision Record (or coupled ADR set + cover) for grounding, decisiveness, completeness, and internal consistency before it is approved or landed — and to catch the drift that iteration introduces across coupled drafts and the cover. Reports findings; does not auto-fix unless asked.
Create and maintain a roadmap that sequences milestones and the plans, research, and decisions that fulfill them. Use when work spans many artifacts over time and needs one living place that shows the sequence, status, dependencies, and risks.
Create implementation plans following project conventions. Use when planning new features, refactors, or significant changes.
Resume working on an in-progress implementation plan. Finds incomplete plans and provides context to continue.
Review an implementation plan for correctness, feasibility, completeness, and internal consistency before it is approved or implemented — and to catch the reference drift that iteration introduces. Reports findings; does not auto-fix unless asked.
| name | plan-archive |
| description | Archive a completed implementation plan. Moves the plan to archive/ and updates its status to COMPLETE. |
Archive a completed implementation plan after successful implementation.
Identify the plan to archive:
.gumbo/plans/*/ (exclude archive/) for plans that appear complete:
- [x])Verify completion:
task-list.md and count checkboxesUpdate plan files:
Update implementation-plan.md status header:
## Status: ✅ COMPLETE
**Completed:** YYYY-MM-DD
**Commits:**
- `abc1234` - feat(plan-NNNN): Phase 1 - Description
- `def5678` - feat(plan-NNNN): Phase 2 - Description
(Include commits section if the commits array in .plan-state.json is non-empty. List each SHA with its commit message.)
Update task-list.md status:
## Status: ✅ COMPLETE
Update .plan-state.json:
{
"status": "complete",
"completed_at": "2026-01-25T10:30:00Z",
"updated_at": "2026-01-25T10:30:00Z",
"commits": ["abc1234", "def5678"],
...existing fields...
}
(The commits array should already be populated during implementation. Preserve it in the final state.)
Move to archive:
mv .gumbo/plans/NNNN-feature-name .gumbo/plans/archive/
Confirm to user:
**Archived:** `.gumbo/plans/archive/NNNN-feature-name/`
**Status:** ✅ COMPLETE
**Tasks:** X/Y complete
**Completed:** YYYY-MM-DD
**Commits:** N commits (list SHAs if present)
User: /plan-archive 0005
User: /plan-archive
(Claude finds the plan with all tasks complete and archives it)
User: /plan-archive 0003
Claude: Plan 0003-backward-edge-routing has 8/12 tasks complete.
Archive as complete anyway? (y/n)
User: yes
(Claude archives with status showing partial completion)