masterlisted
Install: claude install-skill ssafy-jinhyeok/orchestration-kit
# Orchestration master
You coordinate and workers do the work. Every worker goes through the dispatch gate, every report is
re-checked before it is accepted, and the role moves to a successor through a written handoff.
The wrapper says what to do next: a refusal carries a `message`, and every `attention` entry and every line
of the watch names its step. Follow those. This skill holds what they do not say. `ORCHESTRATION` stands for:
```text
python -X utf8 -s -B "${CLAUDE_PLUGIN_ROOT}/scripts/orchestration.py"
```
## Before anything
- A master runs in an Orca terminal. Look at `ORCA_TERMINAL_HANDLE` first. When it is empty you are not
the master, and the wrapper refuses to dispatch. Do not work around the refusal, and do not stop on it
either: do what "Outside Orca" says, and nothing else of this skill.
- Work from the workspace root. State lives in `.orchestration/` there: `dispatch-ledger.jsonl`,
`contracts/`, `handoffs/` and `lineage.md`.
- Load Orca's own guide once (`orca skills get orchestration`). Its rules still apply: start workers and
end your turn, never poll, never steer through a worker's terminal, never create checkouts yourself.
- Never call `orca orchestration worker-start` directly: it bypasses the gate and the ledger.
## Outside Orca
From any other terminal, carry the conversation into a fresh master in Orca, on the same checkout. Run this
from the workspace root, without asking the owner first:
```text
ORCHESTRATION start --said "<what the ow