Design-doc-driven development¶

CAFleet ships three skills that run spec-driven development as CAFleet-orchestrated teams. Give your coding agent one prompt per stage, in order.

Prompts¶

Create a design doc for <one-line feature description>.

Triggers the cafleet-design-doc-create skill — a Director / Drafter / Reviewer team drafts the design document.

Interview me about design-docs/NNNNNNN-<slug>.

Triggers the cafleet-design-doc-interview skill — a Director + Analyzer pair annotates the document with your answers.

Implement design-docs/NNNNNNN-<slug>.

Triggers the cafleet-design-doc-execute skill — a Director / Programmer / Tester team implements the document.

The contributor-facing description of this loop, including what to pass to each skill, lives in Contributing.

Where output lands¶

Each run produces design-docs/NNNNNNN-<slug>/design-doc.md in your repository. The CAFleet repo's own design-docs/ folder holds real examples produced by this loop.

Watch the team work¶

Every inter-agent message is persisted in SQLite, so you can follow the team's coordination live: open the WebUI timeline for the team's fleet — see Use the admin WebUI.

Invocation syntax¶

See your coding-agent's skill documentation for the literal invocation syntax (Claude Code's /skills, codex's /skills, opencode's skill discovery).