superpowers

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores requirements and design before implementation.

Generate a Mermaid delivery diagram from a plan's tasks.json and save it alongside the plan artifacts.

Execute plan in batches with review checkpoints

Create detailed implementation plan with bite-sized tasks

Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>Since a major project step has been completed, use the code-reviewer agent to validate the work against the plan and identify any issues.</commentary></example> <example>Context: User has completed a significant feature implementation. user: "The API endpoints for the task management system are now complete - that covers step 2 from our architecture document" assistant: "Excellent! Let me have the code-reviewer agent examine this implementation to ensure it aligns with our plan and follows best practices" <commentary>A numbered step from the planning document has been completed, so the code-reviewer agent should review the work.</commentary></example>

Use this agent when a design document has been written and needs review before implementation planning begins. Automatically invoked by the brainstorming skill after the design doc is committed to git. Reviews the design with fresh eyes using parallel sub-agents covering completeness, feasibility, scope, and security. Presents findings ranked by severity and requires explicit resolution of each finding before the brainstorming workflow can proceed to writing-plans. Examples: <example> Context: Brainstorming skill has just committed a design doc to docs/plans/feature/design.md user: "Design doc written and committed." assistant: "Now let me invoke the design-reviewer agent to review the design before we proceed to implementation planning." <commentary> The brainstorming skill mandates design-reviewer after writing the design doc. The agent must be invoked here — writing-plans cannot proceed without it. </commentary> </example> <example> Context: User has completed brainstorming and written a design doc for a new feature. user: "I've finished the design for the authentication system." assistant: "Great. The brainstorming workflow requires a design review before we move to implementation planning. Let me invoke the design-reviewer agent." <commentary> Design doc exists and writing-plans has not yet been invoked — design-reviewer must run first. </commentary> </example>

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Use when planning feature delivery, breaking down a pitch into PRs, mapping deployment order, visualizing feature flags, identifying parallelization opportunities, or discussing dependency bottlenecks between engineering changes.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Use when executing implementation plans with independent tasks in the current session

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

Use when implementing any feature or bugfix, before writing implementation code

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Use when you have a spec or requirements for a multi-step task, before touching code

Use when creating new skills, editing existing skills, or verifying skills work before deployment

1 hook across 1 event