Use when a matching specialist could materially improve accuracy or context isolation, or when a request spans independent work lanes.
Use when implementing a repository feature, integration, API or schema change, or other intentional behavior addition after the desired outcome is clear enough to build.
Use when evaluating or evolving an existing system's architecture, business or domain boundaries, cross-module flows, dependencies, reliability, scalability, security, or operability.
Use when the user wants repository-grounded explanation, technical analysis, a command, or an approach comparison without asking for implementation or remediation.
Use when investigating and repairing a regression, crash, failing test, incorrect output, integration failure, or performance problem in a repository.
Use when inspecting or changing local Git state, including diffs, staging, commits, restores, reverts, and merge, rebase, or cherry-pick conflict resolution.
Use when reading or changing GitHub issues, pull requests, workflow runs, releases, repository metadata, or remote review context through the GitHub CLI.
Use when improving internal structure, dependencies, readability, maintainability, or performance without intentionally changing externally observable behavior.