Use this agent when code has been written or modified and needs to be reviewed from a high-level design and architecture perspective to ensure alignment with documented design principles. This agent should be called proactively after logical code changes are completed, before committing or merging changes. Examples…
Use this agent when you have recently written or modified code that needs a comprehensive review, or when you have committed significant changes that should be reviewed before merging. This agent coordinates multiple specialized reviewers and produces a unified report. Examples: Context: User has just completed…
Use this agent when code needs to be reviewed for implementation quality, correctness, and adherence to coding standards. This agent focuses on the detailed implementation aspects rather than high-level architecture. Examples: Context: User has implemented a new class and wants implementation feedback. user: "Can you…
Use this agent when you need to systematically address code review comments on a pull request. This agent should be invoked when: Context: A pull request has been reviewed and multiple code review comments need to be addressed. user: "Can you help me address the code review comments on PR #123?" assistant: "I'll use…
Use this agent when the user provides or references a Product Requirements Document (PRD) and needs it broken down into actionable development tasks. This agent should be invoked when: The user shares a new PRD or feature specification that needs implementation planning The user asks to break down requirements into…
Use this agent when the user requests creation of a Product Requirements Document (PRD), asks to document a new feature, mentions writing requirements, or describes functionality that needs formal specification. This agent should be launched proactively when: Context: User describes a feature they want to build. user…
Use this agent when the user provides a specific coding task to implement, such as adding a new feature, fixing a bug, or creating a new component. This agent should be invoked when: The user has a clear, well-defined implementation task The user provides requirements or acceptance criteria for code to write The user…
Use this agent when you need to evaluate the test coverage of code changes, identify missing test scenarios, or assess the quality of existing tests. This agent should be invoked when: Context: User has implemented a feature and wants to ensure adequate testing. user: "I've implemented the new…