Menu
Cancel an implementation plan. Moves the plan to archive/ with CANCELLED status. Use when a plan is superseded, abandoned, or no longer needed.
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-cancel |
| description | Cancel an implementation plan. Moves the plan to archive/ with CANCELLED status. Use when a plan is superseded, abandoned, or no longer needed. |
Cancel an implementation plan that is no longer being pursued.
Identify the plan to cancel:
Ask for cancellation reason (optional but recommended):
Update plan files:
Update implementation-plan.md status header:
## Status: ❌ CANCELLED
**Cancelled:** YYYY-MM-DD
**Reason:** [User's reason, if provided]
**Superseded by:** NNNN-other-plan (if applicable)
Update task-list.md status:
## Status: ❌ CANCELLED
Update .plan-state.json:
{
"status": "cancelled",
"cancelled_at": "2026-01-25T10:30:00Z",
"updated_at": "2026-01-25T10:30:00Z",
"cancellation_reason": "Superseded by 0005-dagre-module",
"superseded_by": "0005-dagre-module",
...existing fields...
}
Move to archive:
mv .gumbo/plans/NNNN-feature-name .gumbo/plans/archive/
Confirm to user:
**Cancelled:** `.gumbo/plans/archive/NNNN-feature-name/`
**Status:** ❌ CANCELLED
**Reason:** [reason]
**Progress at cancellation:** X/Y tasks (Z%)
User: /plan-cancel 0004
Claude: Why is plan 0004-declaration-order-layout being cancelled?
User: Superseded by the dagre module plan
Claude: Is this superseded by plan 0005-dagre-module? (y/n)
User: yes
**Cancelled:** `.gumbo/plans/archive/0004-declaration-order-layout/`
**Status:** ❌ CANCELLED
**Reason:** Superseded by 0005-dagre-module
**Progress at cancellation:** 0/14 tasks (0%)
User: /plan-cancel 0004
Claude: Plan 0004 is already in archive/ but shows status IN PROGRESS.
Update status to CANCELLED? (y/n)
User: yes
**Updated:** `.gumbo/plans/archive/0004-declaration-order-layout/`
**Status:** ❌ CANCELLED