round-verification

Verifies a CCB execution round and produces a machine-readable round result artifact.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After an orchestrator finishes an execution round in a multi-agent CCB workflow, someone must decide whether the round passed, needs rework, or requires replanning. This Skill standardizes that judgment by turning orchestrator summaries, worker reports, checker reports, and test evidence into a single machine-readable round result.

Core Features & Use Cases

  • Structured verdict output: Produces one of five explicit results: pass, rework_node, partial, replan_required, or global_blocker.
  • Evidence-based rules: Requires full verification-contract evidence for pass, and constrains each failure verdict to a precise meaning (bounded node repair, preserved independent branches, out-of-loop replanning, or blocked progress).
  • Use Case: In an agentic loop workflow, after the orchestrator returns a round summary with node reports, run this Skill to classify the round as partial so successful independent branches are preserved while dependent branches are marked unfinished.

Quick Start

Verify the latest CCB execution round using the orchestrator summary, worker and checker reports, and command evidence, then output the round result verdict.

Frequently Asked Questions about round-verification

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

FAQPage Schema
How do I verify an execution round in a multi-agent workflow?

Collect the task packet, planner verification contract, orchestrator summary, worker reports, checker reports, and command or test evidence, then apply the round verification rules. The output is a single verdict line such as pass, partial, or replan_required.

What round result values does the verification produce?

The report contains one of five values: pass, rework_node, partial, replan_required, or global_blocker. Each value has a strict definition tied to the available evidence and the scope of the failure.

When should a round be marked partial instead of pass?

Mark partial when some independent branches succeeded with evidence but dependent branches remain unfinished. Pass requires evidence covering the entire verification contract, so any gap rules it out.

What is the difference between replan_required and global_blocker?

replan_required means acceptance criteria, design, split, or constraints must change outside the execution loop. global_blocker means no safe progress is possible at all without user or system intervention.

When is rework_node the correct verdict?

Use rework_node only for bounded node repair, where a specific node can be fixed without changing the plan or affecting other branches. Broader design or constraint problems should be escalated to replan_required.