cf-powers

MANDATORY before implementation. From idea to technical analysis — explores ideas through dialogue, then produces comprehensive analysis with cross-check reviews.

Execute plan in batches with review checkpoints

Create detailed implementation plan with bite-sized tasks

Use this agent when a technical analysis or specification needs review from a business analyst perspective. Examples: <example>Context: A technical analysis has been written. user: "The analysis for the email outbox feature is ready for review" assistant: "Let me dispatch the business-analyst-reviewer agent to check requirements completeness, user workflows, and edge cases" <commentary>Since a technical analysis document has been completed, use the business-analyst-reviewer agent to validate business requirements coverage.</commentary></example> <example>Context: A specification needs business validation before implementation planning. user: "Can you review the VAT rates analysis from a business perspective?" assistant: "I'll have the business-analyst-reviewer agent examine the analysis for completeness and business logic gaps" <commentary>The user explicitly requests business-perspective review of a technical document.</commentary></example>

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 technical analysis or specification needs review from a developer perspective. Examples: <example>Context: A technical analysis has been written and needs technical validation. user: "The analysis for the VAT rates feature is ready -- please review the technical approach" assistant: "Let me dispatch the developer-reviewer agent to check technical feasibility, architecture, and integration points" <commentary>Since a technical analysis needs validation, use the developer-reviewer agent to verify technical soundness.</commentary></example> <example>Context: An analysis needs to be verified against actual code. user: "Can you verify the file references in the email outbox analysis are correct?" assistant: "I'll have the developer-reviewer agent read the codebase and verify all claims in the analysis" <commentary>The user wants code-level verification of the analysis -- the developer-reviewer reads actual files.</commentary></example>

Use this agent when a technical analysis, specification, or implementation needs review from a performance perspective. Examples: <example>Context: A technical analysis has been written. user: "Check the reporting feature analysis for performance issues" assistant: "Let me dispatch the performance-reviewer to check database patterns, indexes, and scalability" <commentary>Use the performance-reviewer for data-heavy features.</commentary></example> <example>Context: Code changes touch database queries or data processing. user: "Review the search implementation for performance" assistant: "I'll have the performance-reviewer check query patterns, indexes, and caching" <commentary>Search is performance-sensitive — check for N+1 queries and missing indexes.</commentary></example>

Use this agent when a technical analysis, specification, or implementation needs review from a security perspective. Examples: <example>Context: A technical analysis has been written. user: "Please review the API gateway analysis for security concerns" assistant: "Let me dispatch the security-reviewer agent to check trust boundaries, attack vectors, and authentication" <commentary>Use the security-reviewer to validate security posture.</commentary></example> <example>Context: Code changes touch authentication or data handling. user: "Review the session management changes for security" assistant: "I'll have the security-reviewer agent examine trust boundaries and bypass risks" <commentary>Security-critical paths need the security-reviewer.</commentary></example>

Use for non-trivial implementations involving design choices, multiple components, or unclear requirements. Explores ideas through dialogue, then produces a technical analysis with architecture, phases, risks, and cross-check reviews. SKIP for mechanical/single-file changes (Dockerfile, CI YAML, config tweak, one-liner) or when the user has already specified exactly what to build.

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

Use when implementation of a feature, fix, or refactor is finished, before claiming work complete or starting merge/PR — any change that may affect docs/, README, CHANGELOG, or inline docstrings/JSDoc

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

1 hook across 1 event