Slash Command

/plan

Decomposes specs into shippable milestones with tasks, sizing, dependencies, risk register, and deferred items. Produces versioned plan artifact.

developer-tools

npx claudepluginhub rjmurillo/ai-agents --plugin project-toolkit

Details

Argumentspec-output-or-issue-number

Referenced Files

CLAUDE.md

Allowed Tools

TaskSkillReadWriteGlobGrep

Prompt Preview

@CLAUDE.md

Plan: $ARGUMENTS

If $ARGUMENTS is empty, check for recent /spec output in the conversation. If none found, ask the user what to plan.

## Process

1. Read the spec or issue
2. Map sub-problems to existing code (what already exists? use Grep/Glob to verify)
3. Task(subagent_type="milestone-planner"): You are a project planner. Break the spec into milestones with clear exit criteria. Each milestone is independently shippable. Sequence by dependencies. Flag parallel opportunities.
4. Task(subagent_type="task-decomposer"): You are a work breakdown specialist. Decompose each milesto...

Command Content

Other plugins with /plan

/plan

27.2k

Breaks project into small verifiable tasks with acceptance criteria, dependencies, checkpoints. Reads spec/codebase, presents plan for review, saves to tasks/plan.md and tasks/todo.md.

agent-skills

/plan

1.0k

Generates a structured implementation plan with goal, phases, small tasks, dependencies, risks, milestones, and priorities.

plan

/blueprint

242

Generates an implementation plan with system architecture design, component interfaces, data flow, and dependency-ordered task breakdown from a specification. Supports --input FILE and --component NAME.

attune

/plan

Decomposes feature spec into executable plan with automatic phase analysis.

spectacular

/plan

173.8k

Restates requirements, assesses risks and dependencies, generates step-by-step implementation plan with complexity estimate, and waits for user confirmation before coding.

everything-claude-code

/plan

20.4k

Starts Manus-style file-based planning: creates task_plan.md, findings.md, progress.md if missing, invokes planning skill, and guides through workflow.

planning-with-files

Stats

Parent Repo Stars26

Parent Repo Forks4

Last CommitApr 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

@CLAUDE.md Plan: $ARGUMENTS If $ARGUMENTS is empty, check for recent /spec output in the conversation. If none found, ask the user what to plan. ## Process 1. Read the spec or issue 2. Map sub-problems to existing code (what already exists? use Grep/Glob to verify) 3. Task(subagent_type="milestone-planner"): You are a project planner. Break the spec into milestones with clear exit criteria. Each milestone is independently shippable. Sequence by dependencies. Flag parallel opportunities. 4. Task(subagent_type="task-decomposer"): You are a work breakdown specialist. Decompose each milesto...

@CLAUDE.md

Plan: $ARGUMENTS

If $ARGUMENTS is empty, check for recent /spec output in the conversation. If none found, ask the user what to plan.

Process

Read the spec or issue
Map sub-problems to existing code (what already exists? use Grep/Glob to verify)
Task(subagent_type="milestone-planner"): You are a project planner. Break the spec into milestones with clear exit criteria. Each milestone is independently shippable. Sequence by dependencies. Flag parallel opportunities.
Task(subagent_type="task-decomposer"): You are a work breakdown specialist. Decompose each milestone into atomic tasks. Each task is independently verifiable with a clear done definition. Size by complexity (S/M/L), not time.
Invoke Skill(skill="execution-plans") to persist the plan as a versioned artifact.
Task(subagent_type="analyst"): You are a risk analyst. Run a pre-mortem on this plan. What fails first? What dependencies are fragile? What assumptions are untested?
Task(subagent_type="critic"): You are a plan reviewer. Validate: is scope complete? Can tasks execute in the stated sequence? Are estimates credible? Is anything missing?

Evaluation Axes

Scope integrity - Nothing unnecessary, nothing missing
Dependency ordering - Can tasks execute in the stated sequence?
Risk coverage - All P0 risks have mitigations
Estimate confidence - Complexity-based sizing (S/M/L), not time-based
Reversibility - Which steps are hard to undo?

Principles

Programming by Intention: Each task should read like an intent, not an implementation detail.
OODA Loop: Observe (read the spec), Orient (map to existing code), Decide (sequence tasks), Act (commit the plan). Faster loops win.
First Principles: Question the requirement, try to delete the step, then optimize, then speed up, then automate. Never automate something that should not exist.

Output

Structured plan:

Milestones (numbered, with exit criteria)
Tasks per milestone (atomic, with acceptance criteria and S/M/L sizing)
Dependency graph (what blocks what, what can run in parallel)
Risk register (risk, likelihood, impact, mitigation)
Deferred items (explicitly out of scope for this plan)