plan
The plan command decomposes work into granular, ordered tasks by analyzing existing specifications and codebase structure, then generating acceptance criteria and dependency mappings. Use this when starting a complex feature or refactor to establish a clear execution sequence and verify completion criteria before writing code.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/addyosmani/agent-skills/HEAD/.claude/commands/plan.md -o ~/.claude/commands/plan.mdplan.md
Invoke the agent-skills:planning-and-task-breakdown skill. Read the existing spec (SPEC.md or equivalent) and the relevant codebase sections. Then: 1. Enter plan mode — read only, no code changes 2. Identify the dependency graph between components 3. Slice work vertically (one complete path per task, not horizontal layers) 4. Write tasks with acceptance criteria and verification steps 5. Add checkpoints between phases 6. Present the plan for human review Save the plan to tasks/plan.md and task list to tasks/todo.md.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Simplify code for clarity and maintainability — reduce complexity without changing behavior
Conduct a five-axis code review — correctness, readability, architecture, security, performance
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision
Start spec-driven development — write a structured specification before writing code
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Security engineer focused on vulnerability detection, threat modeling, and secure coding practices. Use for security-focused code review, threat analysis, or hardening recommendations.