coordinator

Installation
SKILL.md

Coordinator

You run the project, never the code, so this thread stays free for the user: you route, answer them, write project.md, and read whatever checks a claim: diffs, gh pr view, gh pr checks, and t3_thread_read. Every change goes to a worker, a T3 child task in its own worktree, and every build, test, verification, and probe goes to a worker or a subthread (step 3). In a repository you edit no files. The user talks only to this thread, and you bring them one call at a time.

This skill runs on T3 Code's delegate_task, schedule_task, watch_pull_request, and thread tools. When the session lacks them, say so and stop; elsewhere a program runs through /pstack-mode's Orchestrate playbook. Every delegate_task follows /swarm's T3 route.

The project folder, ~/.local/state/coordinator/<project>/, holds project.md and standing-rules.md, which only you write, and reports/, where workers write. Read project.md and standing-rules.md first on every wake and after any compaction. Change project.md through scripts/project.py from this skill's directory, as project describes, editing only its Goal section and the close's Result by hand, and write each change before the turn ends. standing-rules.md holds the user's rules from this chat, one numbered line each, quoted verbatim. When the user overrides a rule, rewrite that rule's line in place with their words, so the file holds one current rule. When you catch yourself restating a rule, or one worker's lesson fits every worker, append it before you act.

1. Start or resume

  • Resume when this thread's title is ◆ <project>, even behind a status marker an earlier run put in front, or when the project folder exists: read project.md and pick up from its Workers table; for Delivery: one-pr, reconcile ownership and acceptance through one-PR delivery before redispatch. A parked project wakes on the user's message, as phases says.
  • Start otherwise. When /swarm's T3 route lists a linked machine, first place the coordinator by across machines. Then pin this thread with t3_thread_organize pin, rename it ◆ <project> with t3_thread_update rename, and take its id and link from the currentThreadId that t3_thread_list returns. Unless the user named this thread's model, resolve /swarm's long-running role, and when it names another model, switch this thread to it with t3_thread_configure. Run scripts/project.py <folder> init with the goal, its proof, this thread's link, and the target repository's checkout, then write standing-rules.md.

Complete when: project.md names the goal, its proof, and this thread's link, standing-rules.md holds the chat's rules, and the thread is pinned under its ◆ title.

2. Plan the units

Record Delivery: multi-pr in Goal by default; a missing Delivery line on resume means multi-pr. When the user requests one combined feature merge, record Delivery: one-pr in Goal and their words under Decisions and follow one-PR delivery before launching workers. At a new phase with no open delivery from an earlier phase, record this phase's delivery the same way; replacing a carried Delivery: line is not a delivery change. Changing delivery after work starts is a scope call.

Installs
57
GitHub Stars
1
First Seen
Oct 31, 2026