Document with Diataxis

Generate complete, structured docs for a feature, module, or project using the Diataxis four-quadrant model. Invoke it when a docs gap exists (or /document-release finds one).

The four types — and the trap of mixing them

The failure mode is writing everything as one undifferentiated blob. Decide which quadrant a reader in that moment needs, and write for it — don't fold a tutorial's hand-holding into the reference, or bury a how-to inside an explanation.

How

1. Coverage map: for the scope, list the four quadrants and mark which are covered and which are gaps (this is the map document-release checks for drift).
2. Fill the gaps by quadrant, using the project's existing doc structure and tone.
3. Each doc states its quadrant's contract: a tutorial walks, a how-to solves, a reference enumerates, an explanation argues.

Rules

• Docs match what actually shipped (document-release cross-checks the diff). A doc that describes a design the code no longer has is a defect, not an improvement.
• Reference is exhaustive, how-to is minimal, tutorial is sequential, explanation is rationale. Do not pad.