
Use when the DevOp is diagnosing OS issues, network problems, permission errors, disk space, memory constraints, DNS resolution, port conflicts, or service crashes. Activates when debugging infrastructure, environment, or system-level problems.
Use when the Production Engineer is validating a branch for production merge, running pre-release checklists, performing regression testing, benchmarking performance, or analyzing the impact of changes before merging to main. Activates for any release readiness assessment.
Use when the Integrator is writing unit tests, e2e tests, designing test strategies, improving test coverage, creating test fixtures, or mocking dependencies. Activates for any testing-related work including TDD, test refactoring, or test debugging.
Use when the DevOp is setting up CI/CD pipelines, configuring GitHub Actions, GitLab CI, build automation, deployment strategies (blue-green, canary, rolling), or managing build artifacts. Activates for pipeline creation, build optimization, or deployment configuration.
Use when the Architect is reviewing code changes, evaluating pull requests, assessing implementation quality, checking for security issues, or verifying code follows architectural patterns. Activates for any code review, implementation evaluation, or quality assessment.
Use when the Integrator is managing project dependencies, updating packages, resolving version conflicts, auditing for vulnerabilities, or maintaining lock files. Activates when working with package.json, requirements.txt, Cargo.toml, or any dependency configuration.
Use when the Integrator is performing git operations — committing, branching, merging feature branches, resolving conflicts, managing branch lifecycle, or maintaining commit history. Activates for any git-related work.
Use when the Developer is implementing features from task specifications, translating architecture into code, integrating with APIs, managing state, or choosing design patterns. Activates when building new functionality from requirements.
Use when the Manager is prioritizing tasks, planning work, allocating resources, triaging backlogs, resolving blockers, tracking progress, or managing team workload. Activates for sprint planning, capacity assessment, and priority decisions.
Use when the Manager is writing status updates, daily reports, queue messages to team members, escalation notices, or cross-role coordination messages. Activates when composing any team communication, reports, or documentation updates.
Use when the Architect is breaking down change requests into implementable tasks, defining acceptance criteria, estimating task size, mapping dependencies, or creating technical sub-tasks for Developer and Integrator.
Use when the Manager is creating, evaluating, or scoping change requests. Activates when writing CRs, assessing feature requests, estimating effort, analyzing impact, or deciding whether to approve a proposed change.
Use when the Developer is writing or modifying code, implementing features, fixing bugs, or refactoring. Activates for any code writing task to ensure clean, readable, maintainable code following KISS, DRY, and YAGNI principles.
Use when the Developer is investigating bugs, troubleshooting errors, performing root cause analysis, fixing failing tests, or diagnosing unexpected behavior. Activates when debugging, fixing issues, or analyzing error logs.
Use when the DevOp is working with Docker, containers, cloud services, networking, server configuration, storage, compute scaling, or any infrastructure setup. Activates for Dockerfile creation, docker-compose configuration, cloud resource management, or server administration.
Use when the Production Engineer is assessing production health, setting up monitoring, defining health checks, evaluating SLA compliance, or responding to incidents. Activates when discussing production readiness, system health, alerting, or incident response.
Use when the Production Engineer is planning rollback strategies, reverting a bad release, handling data migration reversals, managing feature flags, implementing hotfix workflows, or preparing disaster recovery procedures. Activates when discussing rollbacks, reverts, or recovery from failed deployments.
Use when the Architect is designing system architecture, choosing technology stacks, defining data models, designing APIs, making scalability decisions, or updating ARCHITECTURE.md. Activates for any architecture design, technology evaluation, or system structure discussion.