From gumbo
Cancels implementation plans by moving to archive/, updating status to CANCELLED in Markdown/JSON files, and logging reasons/superseding plans. For abandoned or superseded plans.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gumbo:plan-cancelThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Cancel an implementation plan that is no longer being pursued.
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
npx claudepluginhub kevinswiber/gumbo --plugin gumboArchives a completed or abandoned plan by moving it to an archived folder with metadata and timestamp.
Cancels an active request/task and cleans up associated resources including worktrees and temporary branches. Supports force-cancel. Integrates with plan state synchronization.
Implements approved plans from .claude/scratchpad files by reading code fully, executing phases sequentially, verifying work, and updating checkboxes.