assigned-review-chain

Submits node results to an assigned Reviewer through a bounded pass/rework chain.

3.5k|342|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/bfly123/claude_code_bridge --skill assigned-review-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: assigned-review-chain
Source: https://github.com/bfly123/claude_code_bridge/tree/main/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.coder/skills/assigned-review-chain
Command: npx skills add https://github.com/bfly123/claude_code_bridge --skill assigned-review-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In multi-agent CCB workflows, a Coder agent must not declare its own work complete; this Skill enforces a disciplined handoff where one assigned Reviewer validates each node result before the Coder can finish.

Core Features & Use Cases

  • Bounded Review Submission: Sends the node result to the single assigned Reviewer using command ask --chain --artifact-reply with a structured work packet including allowed paths, acceptance refs, and verification results.
  • Machine-Readable Status Protocol: Requires the Reviewer's first reply line to be exactly status: pass, status: rework_required, status: blocked, or status: non_converged, mapping each to a Coder terminal state (done, blocked, needs_rework).
  • Strict Boundaries: Forbids polling, plain ask, multiple targets, self-claiming done, commits, or releasing agents.
  • Use Case: A Coder agent finishes implementing a node in an agentic loop workflow, submits the change set and verification output to its assigned Reviewer, applies bounded repairs on rework requests, and only returns done after an explicit pass.

Quick Start

Submit my completed node result to the assigned Reviewer using the chained review command and wait for a pass, rework, blocked, or non-converged status before finishing.

Frequently Asked Questions about assigned-review-chain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I submit a node result for review in a CCB agentic workflow?

Run `command ask --chain --artifact-reply <assigned-reviewer>` once per review hop, including the node id, workgroup, work packet ref, allowed paths, acceptance refs, verification results, and changed paths. Then stop and wait for the Reviewer's status line.

What status values can the assigned Reviewer return?

The Reviewer's first non-empty reply line must be exactly one of: status: pass, status: rework_required, status: blocked, or status: non_converged. These map to Coder terminal states done, blocked, or needs_rework.

Can I send the review request to a different Reviewer or multiple targets?

No. The same assigned Reviewer named in the node task is the only allowed target for every bounded review hop. Plain ask, --silence, multiple targets, and other roles are explicitly forbidden.

What should I do when the Reviewer returns rework_required?

Apply only the requested bounded repair, rerun verification, and ask the same Reviewer again with --chain. Do not expand scope beyond the requested fix, and stop after resubmitting.

Why can't the Coder claim done before the Reviewer passes?

The protocol requires explicit Reviewer approval as the only path to terminal done. Claiming done early, creating commits, or releasing agents violates the workflow boundaries and breaks the review chain's accountability.