Docs Writer

Recommended effort: high for PRD, Design Doc, and TDD (multi-phase discovery).

Generate structured documents through guided discovery. 4 document types, each with its own workflow depth. Use ultrathink for PRD validation and Design Doc trade-off analysis.

Workflow

trigger --> detect type --> load reference --> discovery --> drafting

Detect document type from the trigger. If ambiguous, ask the user which type they want.

Triggers

| Trigger Pattern | Type | Reference | | ----------------------------------------------------------- | ---------- | --------------------------------- | | Create PRD, define product, product requirements, write PRD | PRD | prd.md | | Create design doc, design system | Design Doc | design.md | | Create TDD, technical design document, technical design | TDD | tdd.md | | Create document, write doc | Ask user | -- |

Notes:

discovery.md is not a direct trigger. It is auto-loaded by prd.md, design.md, and tdd.md at the start of the discovery phase.
quality.md is not a direct trigger. It is auto-loaded by prd.md, design.md, and tdd.md before presenting the document draft.
brief.md is not a direct trigger. It is loaded by prd.md during the drafting phase.

Cross-References

discovery.md -----> prd.md, design.md, tdd.md (auto-loaded before discovery starts)
quality.md -------> prd.md, design.md, tdd.md (auto-loaded before presenting draft)
PRD -------------> Design Doc     (PRD feeds requirements, context into Design Doc)
PRD -------------> TDD            (PRD feeds requirements into TDD)
PRD -------------> epic-tracker   (PRD milestones and FRs inform epic definition)
PRD -------------> design-builder (PRD + Brief inform copy and design extraction)
PRD -------------> spec-driven    (PRD milestones feed spec initialization)

Notes:

PRD: Product requirements only -- problem, users, scope, journeys, business rules, success metrics. Never includes implementation, architecture, tech stack, UI components, or API specs. Those belong to Design Doc, TDD, or design-builder.
Brief: 1-page executive summary of the PRD. Generated automatically during PRD drafting from data already collected; never has its own trigger or discovery phase.
Design Doc: When PRD exists, the Design Doc focuses on technical strategy; without PRD, it covers both product context and technical design. Use Design Doc for informal trade-off discussion.
TDD: Prescriptive technical planning for specific components. A project can have both a Design Doc (system-level decisions) and TDDs (component-level technical plans).
epic-tracker: PRD milestones and functional requirements feed epic planning -- epics, stories, and bugs are managed by epic-tracker
design-builder: PRD sections 1, 3-4 (problem, personas, scope) and Brief (value prop, market) inform copy extraction and design extraction
spec-driven: PRD milestones feed feature initialization -- each milestone can generate a spec with its own tasks

Guidelines

DO:

Always complete discovery before drafting (for types that require it)
Review the artifact before presenting to user (load quality.md)
Present draft for user feedback before saving
Mark unknowns as TBD rather than inventing constraints
Use concrete, measurable requirements
Use fixed filenames per type
Detect document type from the trigger; ask if ambiguous
Keep each document within its domain (PRD = product, Design Doc/TDD = technical)

DON'T:

Skip discovery for types that require it
Assume document type -- detect from trigger or ask
Include visual/design direction in product or technical docs
Use vague adjectives as requirements ("fast", "easy", "intuitive")
Mix document types in a single file

Output

All documents save to .artifacts/docs/. Create the directory if it doesn't exist.

| Type | Filename | | ---------- | ----------- | | PRD | prd.md | | Brief | brief.md | | Design Doc | design.md | | TDD | tdd.md |

Error Handling

No .artifacts/docs/: Create the directory
Ambiguous trigger: Ask user which document type
Missing context for discovery: Ask questions, never assume

Compact Instructions

Preserve:

Document type being written, current phase (discovery/validation/synthesis/drafting)
All discovery topic answers collected so far
Agreed scope, priorities, and open TBDs
User confirmations received

Drop:

Raw question-and-answer transcript
Intermediate analysis scratch work