PROACTIVELY USE this agent when you need to identify, analyze, and create mitigation strategies for project risks including technical, schedule, resource, and business risks. This agent MUST BE USED for risk management and mitigation strategy tasks. Examples: <example>Context: User is starting a critical project with tight deadlines and wants to proactively manage potential issues. user: 'We're building a payment processing system with a strict regulatory deadline. What risks should we plan for?' assistant: 'I'll use the risk-manager agent to identify potential technical, compliance, and schedule risks for your payment system project.' <commentary>Since the user is working on a high-stakes project with regulatory requirements, use the risk-manager agent to identify and plan for various project risks.</commentary></example> <example>Context: User is midway through a project and encountering unexpected challenges. user: 'Our API integration is taking longer than expected and we're behind schedule. How should we handle this?' assistant: 'Let me use the risk-manager agent to assess the current situation and develop mitigation strategies for the schedule delays and integration challenges.' <commentary>The user is facing project risks that need immediate assessment and response planning.</commentary></example>

Use this agent when you need to manage Git operations, organize commits, clean up repository history, or optimize Git workflows. This includes deciding how to break down changes into logical commits, cleaning up messy commit history through squashing or reordering, managing branch strategies, resolving merge conflicts, performing repository maintenance, and optimizing Git workflows for collaboration. Examples: <example>Context: User has multiple uncommitted changes across different features that need to be organized. user: 'I have changes for authentication, UI updates, and bug fixes all mixed together. How should I commit these?' assistant: 'I'll use the git-manager agent to analyze your changes and create a logical commit strategy.' <commentary>Since the user needs help organizing multiple changes into logical commits, use the git-manager agent to create a proper commit strategy.</commentary></example> <example>Context: User's feature branch has a messy commit history before merging to main. user: 'My feature branch has 15 commits with typo fixes and work-in-progress commits. Can you clean this up before I merge?' assistant: 'I'll use the git-manager agent to clean up your commit history and prepare it for merge.' <commentary>Since the user needs commit history cleanup and organization, use the git-manager agent to handle the repository maintenance.</commentary></example>

PROACTIVELY USE this agent when project requirements identify gaps in current agent capabilities that require new specialized agents with specific expertise or tool access. This agent MUST BE USED for creating new specialized agents. Examples: Context: Project needs specialized functionality not covered by existing agents, such as barcode scanning integration. user: 'Our library system needs barcode scanning for book check-in/check-out, but none of the existing agents handle hardware integration.' assistant: 'I'll use the agent-creator agent to design and create a specialized barcode-integration agent with the proper Claude Code agent definition file.' Since the project needs specialized barcode integration functionality that doesn't exist in current agents, use the agent-creator to generate a new agent definition file. Context: Domain-specific expertise is needed that current agents don't provide. user: 'We need an agent that understands library cataloging standards like MARC21 and Dublin Core for proper metadata management.' assistant: 'I'll use the agent-creator agent to create a library-cataloging-specialist agent that understands these metadata standards.' Since specialized library science knowledge is needed beyond current agent capabilities, use the agent-creator to create a domain-specific agent.

PROACTIVELY USE this agent when you need to design new RESTful APIs, create or update OpenAPI specifications, standardize existing API endpoints, plan API versioning strategies, or ensure consistent API patterns across your application. This agent MUST BE USED for any API design or endpoint creation tasks. Examples: <example>Context: User is building a library management system and needs to design API endpoints for book management. user: 'I need to create API endpoints for managing books in my library system - CRUD operations, search, and filtering' assistant: 'I'll use the api-designer agent to create a comprehensive RESTful API design for your book management system' <commentary>Since the user needs API design for book management, use the api-designer agent to create proper REST endpoints with HTTP methods, status codes, and data structures.</commentary></example> <example>Context: User has inconsistent API patterns across their application and wants to standardize them. user: 'My existing APIs are inconsistent - some use different naming conventions and HTTP status codes. Can you help standardize them?' assistant: 'I'll use the api-designer agent to analyze your current APIs and create a standardized design pattern' <commentary>Since the user needs API standardization, use the api-designer agent to review existing patterns and create consistent API guidelines.</commentary></example>

PROACTIVELY USE this agent when you need comprehensive validation of system designs, architectural decisions, or technical specifications before implementation begins. This agent MUST BE USED for design validation and architectural review tasks. Examples: <example>Context: User has completed their system design and wants comprehensive validation before implementation. user: 'I've finished designing my microservices architecture. Can you review it to identify any potential issues or improvements?' assistant: 'I'll use the design-reviewer agent to perform a comprehensive review of your architecture design.' <commentary>Since the user has a completed design that needs validation and review, use the design-reviewer agent to validate designs before implementation begins.</commentary></example> <example>Context: User has created a database schema design and wants it reviewed for optimization and best practices. user: 'Here's my database schema for the e-commerce platform. Can you check if it follows normalization principles and identify any performance concerns?' assistant: 'I'll launch the design-reviewer agent to analyze your database schema design for normalization, performance, and best practices.' <commentary>The user has a specific design artifact that requires expert review and validation, making this a perfect use case for the design-reviewer agent.</commentary></example>

PROACTIVELY USE this agent when you need to establish quality assurance processes, coordinate testing activities, define quality standards, or ensure deliverables meet quality requirements throughout the project lifecycle. This agent MUST BE USED for quality assurance and testing coordination tasks. Examples: <example>Context: User wants to ensure their software project maintains high quality standards throughout development. user: 'We need to establish quality processes for our new product development to ensure we deliver bug-free software' assistant: 'I'll use the qa-coordinator agent to establish comprehensive quality assurance processes and testing strategies for your project.' Since the user needs to establish quality processes and testing coordination, use the qa-coordinator agent to create comprehensive QA strategies.</example> <example>Context: User has completed a feature and needs quality gates established before deployment. user: 'I've finished implementing the user authentication module. What quality checks should we run before releasing it?' assistant: 'Let me use the qa-coordinator agent to define the appropriate quality gates and testing strategy for your authentication module.' Since the user needs quality assurance guidance for a specific deliverable, use the qa-coordinator agent to establish testing protocols.</example>

PROACTIVELY USE this agent when you need to coordinate user acceptance testing activities, including creating UAT plans, managing test scenarios, facilitating testing sessions with business users, collecting feedback, and ensuring the system meets real-world business requirements before production deployment. This agent MUST BE USED for user acceptance testing coordination tasks. Examples: <example>Context: Development team has completed a library management system and needs business validation before go-live. user: 'We need to get the system tested by actual library staff before launch.' assistant: 'I'll use the uat-coordinator agent to organize comprehensive user acceptance testing with your library staff.' <commentary>Since the user needs business user testing coordination, use the uat-coordinator agent to create UAT plans and coordinate testing sessions.</commentary></example> <example>Context: System features are ready and stakeholders want to validate functionality meets their needs. user: 'The librarians want to test the new book checkout process to make sure it works for their daily workflow.' assistant: 'Let me use the uat-coordinator agent to set up focused UAT sessions for the checkout process with your librarian staff.' <commentary>The user needs specific workflow validation, so use the uat-coordinator agent to organize targeted testing.</commentary></example>

PROACTIVELY USE this agent when you need to design comprehensive data architectures, database schemas, data models, or data integration strategies. This agent MUST BE USED for any data architecture design or data modeling tasks. This includes creating Entity Relationship Diagrams (ERDs), planning data migration strategies, designing multi-tenant data structures, data warehousing solutions, real-time data processing architectures, or addressing data governance and performance requirements. Examples: <example>Context: User needs to design how data will be structured and managed across their system. user: 'I need to design a database schema for a multi-tenant SaaS application with complex reporting requirements' assistant: 'I'll use the data-architect agent to design an efficient data architecture that supports multi-tenancy and complex reporting.' Since the user needs comprehensive data architecture design for a complex system, use the data-architect agent.</example> <example>Context: User is working on a system that needs to handle large volumes of data efficiently. user: 'Our current database is struggling with performance as we scale. We need to redesign our data architecture.' assistant: 'Let me use the data-architect agent to analyze your current data architecture and design a scalable solution that addresses your performance concerns.'</example>

PROACTIVELY USE this agent when you need a comprehensive code quality assessment after completing significant code changes, implementing new features, refactoring existing code, or before merging pull requests. This agent MUST BE USED after any significant code implementation to ensure quality and security standards. Examples: <example>Context: The user has just implemented a new authentication system and wants to ensure code quality before deployment. user: 'I've just finished implementing JWT authentication for our API. Here's the code...' assistant: 'Let me use the code-reviewer agent to perform a comprehensive review of your authentication implementation.' <commentary>Since the user has completed significant code changes (authentication system), use the code-reviewer agent to assess code quality, security vulnerabilities, and best practices.</commentary></example> <example>Context: The user has refactored a large component and wants to verify the changes maintain quality standards. user: 'I've refactored the user management component to improve performance. Can you check if everything looks good?' assistant: 'I'll use the code-reviewer agent to thoroughly review your refactored user management component.' <commentary>Since the user has completed a refactoring (significant code change), use the code-reviewer agent to ensure the refactoring maintains code quality and doesn't introduce issues.</commentary></example>

PROACTIVELY USE this agent when you need to create, configure, or improve continuous integration and deployment pipelines. This agent MUST BE USED for any CI/CD pipeline setup or automation tasks. This includes setting up automated workflows for testing, building, and deploying applications across various CI/CD platforms like GitHub Actions, GitLab CI, Jenkins, or Azure DevOps. Examples: <example>Context: User wants to set up automated deployment for a Node.js application. user: 'I need to create a CI/CD pipeline for my Node.js app that runs tests and deploys to production' assistant: 'I'll use the cicd-builder agent to create a comprehensive CI/CD pipeline with automated testing and deployment workflows' <commentary>The user needs CI/CD pipeline setup, so use the cicd-builder agent to design and implement the automation workflows.</commentary></example> <example>Context: User has a project that needs automated quality gates and security scanning. user: 'Can you help me add security scanning and code quality checks to our deployment process?' assistant: 'I'll use the cicd-builder agent to enhance your pipeline with security scanning and quality gates' <commentary>Since the user needs CI/CD improvements with security and quality features, use the cicd-builder agent.</commentary></example>