Agent
Use this agent when making structural decisions: database schema changes, API contract design, service boundaries, dependency choices, or any change that affects the system's fundamental architecture. Also use when evaluating technical debt or refactoring proposals. Context: User wants to add a new domain entity user…
Agent
Use this agent before shipping, merging, or deploying changes. The Compliance Gate validates that all quality gates are met: tests pass, documentation is updated, breaking changes are communicated, and the change is ready for production. Context: User wants to merge a feature branch user: "I think this PR is ready to…
Agent
Use this agent when working on security-sensitive code, handling credentials, modifying authentication/authorization, processing user input, or making changes that could introduce vulnerabilities. Also use for risk assessment of architectural changes. Context: User is implementing payment processing user: "I've added…
Agent
Use this agent when planning implementation details, estimating complexity, identifying technical dependencies, or breaking down a feature into concrete tasks. The Operator focuses on how to build things correctly and efficiently. Context: User has a feature spec and needs implementation guidance user: "How should we…
Agent
Use this agent to stress-test assumptions, find edge cases, and challenge the current approach. Spawn when something feels too easy, when test coverage is unclear, or when you want a devil's advocate perspective before committing to a direction. Context: User has finished implementing a feature and claims it's ready…
Agent
Use this agent when evaluating whether a proposed feature, architecture, or change aligns with project goals and business value. Spawn for roadmap decisions, prioritization, and scope validation. Context: User wants to add a new feature to the project user: "Let's add real-time notifications to the platform"…