From gumbo
Archives completed implementation plans in .gumbo/plans/: verifies task checkboxes, updates status/JSON with completion date/commits, moves to archive/. Use after implementation.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gumbo:plan-archiveThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Archive a completed implementation plan after successful implementation.
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)
npx claudepluginhub kevinswiber/gumbo --plugin gumboArchives a completed or abandoned plan by moving it to an archived folder with metadata and timestamp.
Tracks task completion in markdown plan files using plan-file-management subcommands. Mandates test verification of observables and evidence before marking tasks done. Activates on *-plan.md files.
Manages execution plans as versioned Markdown artifacts with progress tracking, decision logs, and archiving in .agents/plans. Use for creating, updating, or archiving plans in complex multi-step work.