fleetlisted
Install: claude install-skill Wang-Cankun/cankun-skills
# Fleet
Invoking this skill is the user's opt-in for the whole run, to multi-agent orchestration and to
every model in the roster, as ultracode is for Claude-only workflows: author and run a Workflow
for every substantive step, one per phase when the work has several.
**Stages produce; this session accepts.** Give stages the work that produces: surveying code,
implementing, fixing, researching, hunting for problems, first reviews, drafting prose. Keep
here the work that accepts: what the task is and what done means, and whether a result holds
before anything relies on it (a merge, a reported number, a decision). How deep each acceptance
goes is your judgement, from what a wrong acceptance would cost. UI look stays with Claude.
Read the user's crew preferences (`~/.codex/agent-notes/crew.md`, when present) before
writing the script: they set the coordinator's role, the flow of each unit and the
review policy, and win over this skill where they differ.
## Choosing models
Read the user's model roster (`~/.codex/agent-notes/models.md`, when present) before writing
the script: which model does which kind of stage, its route and effort on this machine, and how
to steer it. Without a roster, choose from the models this machine's CLIs offer and tell the
user which. Put each stage's model, by full version, in its label (`review:<model>-<effort>`).
- Code from a brief you can settle up front, with checks that tell right from wrong, goes to
the model the roster names for buildin