OpenParable
Skip to content
← Back to skills

plan:cancel

Productivity

plan:cancel is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Cancel an implementation plan. Moves the plan to archive/ with CANCELLED status. Use when a plan is superseded, abandoned, or no longer needed.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/plan-cancel/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/plan-cancel, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Cancel Skill

Cancel an implementation plan that is no longer being pursued.

Process

  1. Identify the plan to cancel:

    • If the user specifies a plan number/name, use that
    • Otherwise, list in-progress plans and ask user to choose
    • Never auto-cancel - always require explicit identification
  2. Ask for cancellation reason (optional but recommended):

    • "Why is this plan being cancelled?"
    • Common reasons: superseded by another plan, requirements changed, no longer needed
    • If superseded, ask which plan supersedes it
  3. 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...
    }
    
  4. Move to archive:

    mv plans/NNNN-feature-name plans/archive/
    
  5. Confirm to user:

    **Cancelled:** `plans/archive/NNNN-feature-name/`
    **Status:** ❌ CANCELLED
    **Reason:** [reason]
    **Progress at cancellation:** X/Y tasks (Z%)
    

Example Usage

Cancel with reason

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:** `plans/archive/0004-declaration-order-layout/`
**Status:** ❌ CANCELLED
**Reason:** Superseded by 0005-dagre-module
**Progress at cancellation:** 0/14 tasks (0%)

Cancel already-archived plan (update status only)

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:** `plans/archive/0004-declaration-order-layout/`
**Status:** ❌ CANCELLED