Design Document Skill (CAFleet Edition)

This skill is the umbrella for the full design-document lifecycle: the standardized format spec plus three CAFleet-native orchestration workflows (create, validate/interview, implement/execute). It is a dispatcher — consult a reference page for the format, or route to the matching workflow body to run a team.

Assigned teammates load this skill through the executing backend's supported loader. Codex/OpenCode use absolute paths for this core, CAFleet core, their own backend section and required role references. Continue the existing assigned workflow; loading this umbrella as a member creates no second team. Main-session user requests follow Dispatch below.

Required reading

Before routing into a workflow or consulting a reference page, Read your overlay — it is row #1 below. Identify your coding agent first: your spawn prompt's CODING AGENT: line names it; a standalone / main-session reader uses its own identity.

Load-bearing — Read before acting:

#	Read	What you lose if you skip it
1	your overlay section ../cafleet/reference/coding-agents.md#<name> — read and resolve it (see Resolve your overlay in the cafleet SKILL.md)	you skip resolution — the failure modes Resolve your overlay closes, e.g. a literal {bg_run} emitted unresolved

On-demand — consult directly (no team), only when the task needs it:

Read	When
reference/guidelines.md	you are writing or checking a doc against the standard structure (the template opens the page), or need section guidelines, quality standards, or formatting rules
reference/coordination.md	you need the inter-member verb + pointer + COMMENT(role) schema

Each workflow body (create / interview / execute) carries its own Required-reading block for the team it runs — base-dir, supervision, and coordination are gated there, not on this dispatch surface.

Dispatch

For a main-session user request matching a scenario below, invoke this skill and run the linked workflow as a full CAFleet team — proactively, the moment the request matches, without waiting for the user to say "use cafleet".

Routing into a workflow means executing its entire orchestration. The Director bootstraps the fleet and its monitor member in one command (cafleet fleet create --monitor-file <path>; the monitor member launches the wake loop in its own pane and reports monitor live, gating the ordinary spawns), then spawns the role team, then the workflow body's review and revision rounds run through to approval. The linked workflow body is the authoritative procedure.

When the user wants to…	Invoke this skill and run
Create a design doc / specification / technical spec	the create workflow (create/create.md) — Director/Drafter/Reviewer team
Validate / review / interview an existing design doc	the interview workflow (interview/interview.md) — multi-round Q&A
Implement / execute a design doc	the execute workflow (execute/execute.md) — TDD team

For the document template, section guidelines, or the coordination protocol — consult the On-demand reference pages in § Required reading above (no team needed).