code-flow

Use when designing the architecture for a new feature or significant change — analyzes existing patterns and produces an implementation blueprint.

Use when you need deep understanding of how a feature or subsystem works before making changes — traces execution paths, maps architecture, and identifies key files.

Use when a major feature, task, or project step has been completed and needs review against requirements and coding standards.

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.

Use when you have a written implementation plan to execute. Orchestrates parallel agent teams, subagents, or serial execution based on the plan's execution strategy.

Use when deciding how to structure work across agents — choosing between agent teams, subagents, or serial execution, and writing effective agent prompts.

Use before any creative work - creating features, building components, adding functionality, or modifying behavior. Discovers requirements and acceptance criteria through collaborative dialogue.

Use when requesting or receiving code review — after completing a feature, before merging, or when acting on review feedback.

Use when implementation is complete and you need to decide how to integrate the work — merge, PR, or cleanup.