The fleet's standard work strategy, packaged as an Agent Skill so any new coordinator session can load it in one reference instead of rediscovering it.
Point a session at SKILL.md. That is the whole interface.
| File | Answers |
|---|---|
SKILL.md |
The loop, the non-negotiables, how to parallelize a wave |
references/SEATS.md |
Which seat runs the work: codex + gpt-5.6-sol, policies, isolation gotchas |
references/REVIEW.md |
Adversarial review before the PR, fresh context, what a real verdict contains |
references/GATES.md |
The merge gate, honest CI checking, the deploy + live-probe ritual |
references/ESCALATION.md |
The three escalation channels and why delivery must be verified |
references/COMMANDS.md |
The gitmoot commands a coordinator actually uses |
This is the strategy — how the fleet works. It is deliberately separate from:
gitmoot/gitmoot→skills/gitmoot/— how to use the gitmoot tool (CLI, result contract, safety).- each project's
AGENTS.md— the facts of that codebase (build, layout, its own footguns).
Every rule here exists because its absence cost something real. When a rule earns an exception, change the rule here rather than working around it in a pane.