cross-agent-reviews

cross-agent-reviews

A multi-host plugin (Claude Code + Codex) that packages a 3-round / 6-step cross-agent spec/plan review pipeline as a single state-driven skill. One slash command — /cr — advances the pipeline based on a project-local state file (.cross-agent-reviews/<slug>/), so operators no longer paste round JSON between rounds on a single host. Reviewer rounds audit the artifact in fresh sessions; author rounds settle findings without requiring a fresh session, with a strict final round preserving cross-agent diversity by construction. Reviews scale to artifact risk: an operator-locked review_profile sets the minimum review breadth and an optional fast mode enables deterministic shortcuts — auto-settling clean rounds and impact-routing verification — without weakening the final independent blocker review (see Review profiles and modes). v0.1.x ships local-only; install via the host's /plugin slash-commands (see Install below).

How it works

Round	Procedure	Role	Input	Output
1a	rounds/1a-audit.md	Reviewer (5-agent parallel review)	spec/plan path	round-1a.json
1b	rounds/1b-settle.md	Author (settle + edit)	round-1a.json	round-1b.json
2a	rounds/2a-audit.md	Reviewer (verify corrections)	round-1b.json	round-2a.json
2b	rounds/2b-settle.md	Author (settle + edit)	round-2a.json	round-2b.json
3a	rounds/3a-audit.md	Reviewer (strict final check)	round-2b.json	round-3a.json
3b	rounds/3b-settle.md	Author (final adjudication)	round-3a.json	final_status (READY_FOR_IMPLEMENTATION or CORRECTED_PENDING_VERIFICATION)
3c	rounds/3c-verify.md	Independent verifier (conditional)	round-3b.json	round-3c.json / round-3c-attempt-NNN.json

Round 3b runs only when Round 3a found blockers. A clean 3a — every reviewer agent ship_ready with zero findings — terminates the pipeline directly (see Terminal status below). Round 3c (final verification) runs only when Round 3b accepted and corrected blockers; a Round 3b that rejected every blocker terminates directly.

In fast mode, a clean 1a/2a audit auto-settles — the empty 1b/2b is generated and persisted with no manual settle round — and 2a/3a verification is impact-routed to the slices touched by accepted findings plus mandatory global and cross-artifact coverage. Any ambiguity, blocker, spec drift, cross-artifact mismatch, or incomplete finding lineage falls back to broad review. Final 3a always keeps full parallel independent reviewer coverage for every slice in its selected scope.

Fresh session per audit round. The router applies a fresh-session preflight before audit rounds (1a, 2a, 3a) and before the verification round (3c) — cross-agent diversity demands the reviewer/verifier come to the artifact without prior interpretive frame. Settle rounds (1b, 2b, 3b) may continue in the same session or a fresh one (operator choice).

Terminal status. The pipeline terminates one of three ways:

• Clean 3a — every Round 3a agent is ship_ready with zero findings. Terminates at Round 3a; Rounds 3b and 3c do not run. final_status: READY_FOR_IMPLEMENTATION.
• Via Round 3b — Round 3a found blockers, Round 3b rejected all of them. final_status: READY_FOR_IMPLEMENTATION; artifact ships unchanged.
• Via Round 3c — Round 3b accepted and corrected blockers, then Round 3c independently verified the corrections. final_status: CORRECTED_AND_READY.

Between Round 3b and a CORRECTED_AND_READY terminal the pipeline holds two non-terminal states: final_verification_pending (3c not yet run) and final_verification_failed (a 3c attempt found unresolved blockers or regressions — fix the artifact and rerun /cr).

Review profiles and modes

review_profile and mode are locked once at artifact-block init and cannot change mid-pipeline. Pass them as order-independent tokens alongside the artifact path:

/cr docs/specs/foo-design.md patch fast

Token	Values	Controls
review_profile	patch · feature · greenfield	Minimum review breadth (slice count, mandatory coverage).
mode	thorough (default) · fast	Whether the deterministic shortcuts the profile allows fire.

• patch — targeted fix, small refactor, or doc correction: most aggressive deterministic reduction.
• feature — new behavior in an existing codebase: moderate reduction; final 3a stays broad until narrower routing is proven safe.
• greenfield — new subsystem or broad architecture: conservative; broad review stays mandatory.

Legacy or absent values preserve the original thorough behavior unchanged.

Suggestion preview