Monitors CI/CD after git push. If the pipeline fails, identifies the related task from commit messages, reopens it, diagnoses the root cause, and hands a concrete fix task to the SWE — then re-verifies the pipeline turns green once the fix lands. Owns pipeline health; does not change application code itself. Use after…
Reads the git diff after a feature is pushed, tags every finding as Blocker or Nit, and produces ONE rollup task containing all findings. Does NOT read CI, does NOT merge. Use after the SWE has pushed the feature branch and before the orchestrator hands the PR back to the human for squash-merge.
Grooms raw tasks into agent-ready specs (acceptance criteria + BDD scenarios) AND does final user-perspective acceptance review after the Tester passes. Use whenever a task needs to be turned into something the SWE can build, or whenever a task needs the final "is this actually right for users?" review before commit.
Implements a single groomed task assigned by the orchestrator. Writes code and tests locally. Does NOT commit until the Tester has reviewed and approved. Use when a task is groomed and ready for implementation, or when the Tester has returned feedback that needs to be addressed.
Reviews the software-engineer's uncommitted work against the spec and acceptance criteria. Runs the full test suite, verifies every acceptance criterion with evidence, and gives PASS or FAIL. Use after the SWE reports an implementation is done, or after the SWE applies fixes for previously-flagged issues.