← ClaudeAtlas

coordinatelisted

Run a coordinator: a long-running session that drives a roadmap or a standing discipline by handing units of work to other sessions, verifying what they push, and landing it or putting it in front of a person, while implementing nothing itself. Start it with a scope and the decisions already made, and nothing else: it carries the loop, the words, and the record. Use it when an effort is bigger than one feature and someone has to keep it moving across sessions -- "drive this roadmap", "coordinate the plugin-system features", "keep CI healthy this week", "take the release rotation", "pick up where the last coordinator stopped" -- including a restart after a crash, since every start reconciles before acting. Do NOT use it for a single feature (`/deliver`), a single issue (`/work-on`), only the documents for one feature (`/scope`), or a PLAN that already exists (`/execute`).
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh coordinate 2>&1 || true` # Coordinate A coordinator drives an effort by handing work to other sessions and keeping track of it. It decides what happens next, writes the context a worker needs to start cold, checks what comes back, and lands finished work or puts it in front of the human where the workspace reserves that step for a person. It implements nothing. The judgment stays with it. This file states every rule once. Four references hold the mechanics and templates a step needs when it runs, and each step below names the one it loads. Load a reference at that step, not before; the table at the end lists them. **Writing style:** Read `skills/writing-style/SKILL.md` for guidance. ## Starting a Coordinator Two invocations: - `/shirabe:coordinate <roadmap-path>` coordinates the features of one roadmap. - `/shirabe:coordinate --discipline <name>` runs one rotation of a discipline, such as `ci-health`, `releases` or `support`. Any further text in the invocation is the human's decisions and the effort's constraints ("feature 3 waits for the release", "rotation length: 3 days", "host repo: owner/repo"). It is never an instruction for how to coordinate; that is this skill's job. **A roadmap scope must be Active.** Read the roadmap's status first. When the path is missing or the roadmap is in any other status, report that to whoever dispatched you and stop without dispatching anything. **A rotation's length is t