Use this agent for the architect phase of a dev-crew run. Invoke before any implementation on features, refactors, schema changes, or anything touching more than one module. Reads the task brief and codebase; produces the plan and the interface/done-criteria contract the rest of the crew builds against.
Use this agent for the release phase of a dev-crew run, only after qa returns an overall PASS. Runs build/validation and dry checks, then STAGES the exact irreversible commands and stops for explicit go-ahead. Never auto-executes a deploy.
Use this agent for the implementation phase of a dev-crew run. Invoke after the architect has produced CONTRACT.md, or directly for small bugfixes. Reads the plan and contract; writes the code and a verification handoff for qa.
Use this agent for deep root-cause or multi-system investigation in a dev-crew run — stubborn, ambiguous, or circling failures that span subsystems, or a bugfix/debug loop that has already exceeded two passes. Reads the symptom and the codebase; produces a diagnosis and a contract the dev role can implement.
Use this agent for the verification phase of a dev-crew run, after dev has written CHANGES.md. Reads the contract and the changes; writes/runs tests and returns a pass/fail verdict per done-criterion. Read-only on source so it can't rewrite what it's checking.
Use this agent when dev-crew initializes in a repo (first run in a repo, or on "re-profile") to scan the project and produce its profile: languages, build tool, frameworks, test and static-analysis stack, CI, deploy targets, and conventions. Read-only and cheap. Writes /.claude/dev-crew/PROFILE.md, which drives…