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:
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
Read durable coordination with message poll/show and inspect the team’s visible panes with member/fleet capture. The Director retains native reception and owns evidence checks until delegated work resolves, preserving host continuation and user gates. Follow the manual lifecycle.
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).