orchestration-bundle-candidate

Generates one validated multi-workgroup orchestration bundle candidate as reply-only JSON evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multi-agent coding work requires deciding how many parallel workgroups a task needs and packaging that decision in a strict, machine-validatable format. This Skill produces exactly one route decision and one adaptive one-to-four-workgroup bundle candidate that a controller can validate and import, without the orchestrator executing anything itself.

Core Features & Use Cases

  • Route Decision: Returns exactly one of direct_execution, needs_detail, macro_adjustment_request, blocked, or partial_completion based on the supplied task packet and execution contract.
  • Adaptive Workgroup Selection: Chooses the smallest justified workgroup count from 1 to 4 using complexity, cutability, dependency evidence, and effective-capacity snapshots, treating capacity as a ceiling rather than a target.
  • Strict Schema Compliance: Emits a JSON bundle conforming to ccb.loop.orchestration_bundle_candidate.v1 with exact root, selection, integration, and policy fields, rejecting structural ambiguity with replan_required evidence.
  • Use Case: An orchestrator agent in the CCB multi-agent loop receives a decomposed task with three independently implementable modules and returns a three-node parallel bundle with bounded work packets, allowed paths, and verification refs for the controller to dispatch.

Quick Start

Activate this skill with the controller-supplied task packet and execution contract, then reply with one route decision and the orchestration bundle JSON candidate.

Frequently Asked Questions about orchestration-bundle-candidate

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

FAQPage Schema
How do I decide how many workgroups to split a coding task into?

Choose the smallest justified count from 1 to 4 based on task complexity, cutability, independently reviewable scopes, and dependency evidence. Use separate nodes only when each has disjoint allowed paths, independent acceptance criteria, and no need to consume a predecessor's newly produced output.

What is the orchestration bundle candidate schema for CCB?

The schema identifier is ccb.loop.orchestration_bundle_candidate.v1, placed in the JSON top-level schema field. Root fields are exactly schema, task_id, bundle_revision, selection, nodes, integration, and policy, with strict constraints on each subfield.

When should parallel nodes versus serial dependencies be used?

Use parallel nodes in the same ready group when units have disjoint allowed paths and can implement against already declared stable interfaces. Add a dependency only when a node genuinely needs a predecessor's newly produced artifact, data, schema, or accepted result.

Can the orchestrator execute commands or dispatch agents directly?

No. The skill is reply-only and must not run ccb commands, provider CLIs, or dispatch any role. The controller validates the candidate, binds agents, submits asks, and handles integration and authority recording.

What happens when verification refs lack direct commands?

If supplied artifacts do not contain Verification sections with direct argv commands, the skill returns structural replan_required evidence instead of emitting an execution bundle. Shell constructs like pipes, &&, or cd are not allowed since commands run without a shell.