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. If tasks/plan.md or tasks/todo.md already exists with unchecked tasks for different work, stop and ask before writing — never silently overwrite an incomplete plan.
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be configured.
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Senior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.
Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.
Simplify code for clarity and maintainability — reduce complexity without changing behavior