superpowers

Deprecated - use the superpowers:brainstorming skill instead

Deprecated - use the superpowers:executing-plans skill instead

Deprecated - use the superpowers:writing-plans skill instead

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 before modifying shared functions, core utilities, class definitions, or database schemas. Maps out all dependencies and referencing symbols to prevent unintended breakage in other files.

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 working on large, multi-service codebases where semantic search and global project context are needed to find relevant code or explain architecture.

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies. Integrated with tmux-workflow for observability and session-distiller for context management.

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

1 hook across 1 event