Implements an approved specification as code changes, creates a git worktree, commits, and opens a pull request. Use when a spec has been approved and needs to be translated into a working PR with passing build and tests.
Writes or revises an implementation specification from an issue, producing the single source of truth a downstream coder agent will use. Use during spec-writing or spec-feedback phases when an issue needs to be turned into an actionable, self-contained spec with file paths, method names, and acceptance criteria.
Reviews a pull request against an approved spec for correctness, security, performance, spec compliance, and style, then issues a verdict that advances or reworks the pipeline. Use when a coder has opened a PR that needs a structured code review before tests or merge.
Verifies that a coder's implementation builds and passes tests both locally and in CI, without modifying code. Use after the coder phase to confirm the PR is green before review, or to route back to coding on failure.
Addresses human review feedback on an existing pull request by implementing requested changes, replying to comments, and pushing an updated commit. Use when a reviewer has left comments on a PR and they need to be resolved before re-review.