For AI agents: the complete documentation index is available at /cafleet/llms.txt, the full documentation bundle is available at /cafleet/llms-full.txt, and this page is available as Markdown at /cafleet/how-to/design-doc-development.md.

Design document workflow

Develop a feature through a reviewed design, an interview and an implementation. The cafleet and cafleet-design-doc skills coordinate the teams; give your coding agent one prompt per stage.

Prompts

Each prompt triggers one cafleet-design-doc workflow:

StagePromptOutcomeTeam
1. DraftCreate a design doc for <one-line feature description>.Clarification, drafting and review, followed by your approvalDirector + Drafter + Reviewer
2. RefineInterview me about design-docs/NNNNNNN-<slug>.Questions and persisted answers, with document annotations for revisionDirector + Analyzer
3. ImplementImplement design-docs/NNNNNNN-<slug>.Implementation and checks, fresh review, then your approvalDirector + Programmer + Tester for code, optional Verifier, then a fresh Reviewer

These stages invoke create, interview and execute respectively. After an interview, resume creation to incorporate its annotations and review the revised design before implementation. Documentation/configuration work may use a Programmer without a Tester. Contributor setup is in Contributing.

Where output lands

Creation writes design-docs/NNNNNNN-<slug>/design-doc.md in your repository. CAFleet assigns a seven-digit, zero-padded number one above the highest existing number in that repository's design-docs/, starting at 0000001. The slug is a short kebab-case description, such as add-search, giving 0000001-add-search. The interview keeps questions and answers in question.md beside it and annotates the design; execution updates the design's task progress while implementing the approved work.

Watch the team work

Every inter-member 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).