orchestrator-capacity
Historical reference for script-owned loop capacity requests. Do not use from provider sessions.
git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge /tmp/orchestrator-capacity && cp -r /tmp/orchestrator-capacity/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_orchestrator/adapters/ccb/skills/orchestrator-capacity ~/.claude/skills/orchestrator-capacitySKILL.md
# Orchestrator Capacity Reference This reference is retained for rolepack history only. It is not projected as an active provider skill for `agentroles.ccb_orchestrator`. Loop capacity is now runner-owned. The orchestrator may recommend the semantic need for capacity, but the supervisor/runner script performs any actual capacity ensure, status, release, routing, and cleanup. ## Provider Boundary - Do not run CCB commands. - Do not inspect runtime capacity from the provider session. - Do not release agents, mutate task status, import artifacts, or route work. - Do not invent agent names, windows, panes, provider profiles, or topology. ## Reply Shape When capacity information is needed, reply with semantic evidence only: - requested profiles and counts; - task packet and verification refs; - blockers or missing evidence; - release-readiness recommendation based on supplied worker/reviewer evidence. The runner owns command execution and treats provider replies as evidence only.
Send a request to a CCB agent with `ask`.
Submit one node result to the assigned Reviewer and finish only after a bounded pass/rework chain.
Execute one scoped implementation or investigation item and return evidence without changing workflow authority.
Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.
Diagnose and recover CCB communication and reply delivery stalls. Use when a user reports a missing CCB_REPLY, stuck ask, agent stuck busy/delivering, queued work behind an active job, cancelled/incomplete reply, empty artifact, callback not continuing, duplicate retry after success, or a CCB mailbox/communication backend that appears stuck.
Compact CCB managed agent conversation context with `ccb compact`. Use when the user writes `$ccb-compact`, `$ccb_compact`, or asks to summarize one or more mounted agent contexts without restarting agents or deleting project state.
Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.
Diagnose a named CCB agent by combining authoritative runtime and job lineage with deep read-only pane inspection, apply bounded recovery when evidence supports it, verify the result, and request authorization before submitting a redacted GitHub issue. Use for `$ccb_diagnose agentname`, `$ccb-diagnose agentname`, or reports that a CCB agent is stuck, disconnected, not continuing, not replying, or showing provider errors.