hogancv/coordinate-agents/coordinate-review

Coordinate Review

Use coordinate_agents_task_inspect and coordinate_agents_task_review for normal Plugin review operations. The Plugin bundles the Runtime and does not require a global coordinate-agents command. If MCP is unavailable, or the user explicitly requests debugging, let <skill-dir> be the absolute directory containing this loaded SKILL.md:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" ...

Review only observable evidence tied to the current Task and repository:

1. Read coordinate_agents_task_inspect and the approved specification.
2. Verify the implementation commit exists and inspect its diff.
3. Check validation evidence for the current commit. Re-run relevant tests when

evidence is missing, stale, from a different environment, or leaves a concrete doubt; independently verify high-risk changes when warranted.

1. Compare every acceptance criterion and negative control.
2. Return exactly one decision: REVIEW_APPROVED or CHANGES_REQUESTED.
3. Record that decision through the MCP Task API; never edit a task JSON file

or manually send a Bus message. Only when MCP is unavailable, or for explicit debugging, use this fallback syntax:

node "<skill-dir>/../coordinate-agents/scripts/runtime-entry.mjs" task review \
  --root "<repository>" --id task-... --decision REVIEW_APPROVED --json

For changes, include concrete feedback. The Runtime preserves it and the next explicit task dispatch includes it in the new IMPLEMENT activation. In an implementation workflow, the coordinator continues authorized rework without asking again; a review-only request ends after the recorded review. When the recorded Session is healthy, that activation reuses the same ExecutionSession; review feedback is written into the existing PTY context. Do not use Codex App Terminal UI automation to reach the Implementer.

The Reviewer does not edit product source, tests, or build configuration. It does not merge, tag, push, publish, or pass the human release gate.