dev-fleet

# Dev Fleet Orchestrator This skill tells the **main session** (the orchestrator — you) how to drive the development agents as a pipeline. The agents live in `agents/`; the main session dispatches each by name via the Agent tool, reads its JSON, and gates on the result. **Two ways to run the pipeline — pick by how much determinism you need:** - **This skill (in-the-loop).** You follow these steps and invoke each agent explicitly. A skill is *instructions you follow*, not a mechanical orchestrator — so it's only as reliable as your adherence. Don't lean on auto-delegation for a stage you care about; name the agent. (A human driving Claude Code can force a stage with an `@agent-…` mention.) - **The `dev-story` Workflow (hands-off, deterministic).** For a guaranteed plan→build→verify→cohere→review→full-suite run, dispatch it via the Workflow tool with the **absolute** `scriptPath` `~/.claude/skills/dev-fleet/dev-story.workflow.js` (a relative path won't resolve from your repo). It moves orchestration into code and hands back a ready-to-merge branch; it mirrors the two-point fact discipline and gates coherence on change size automatically (`coherence: auto|always|never`). See *Running for scale*. See `docs/agent-fleet-architecture.md` for the why. ## The pipeline ``` plan & scope ─▶ verify load-bearing facts ─▶ code-builder ─▶ fact-verifier (gate) ─▶ coherence-check (gate, if complex) ─▶ code-reviewer ─▶ full-suite gate ─▶ [you decide] ─▶ commit-pr (explore ...