generate-docs

Read .arch/state.json first.

GATE CHECK:

• If current_phase is finalization and phases.finalization.document_generated is true: Say "Document already generated. Do you want to regenerate? Say 'yes' to regenerate or review the existing document at output/architecture-document.md."
• If current_phase is not components and current_phase is not finalization, STOP: "Cannot generate documentation. Current phase is [phase]."
• If current_phase is components and phases.components.all_accepted is not true, STOP: "All components must be accepted before generating documentation. Use /status to check which components are pending."

Read ALL architecture files:

• .arch/phase1-evaluation.md
• .arch/phase2-methodology.md
• .arch/phase2-components-overview.md
• .arch/phase2-cross-cutting.md (if exists)
• All files in .arch/components/
• All files in .arch/reviews/ (if any)
• .arch/decisions.md
• .arch/org-context.md

Pre-Generation Validation

Before generating the document, perform these validation steps:

1. End-to-End Request Simulation

Trace 3 critical user journeys through the accepted component designs:

• Happy path: The most common user action — trace through every component it touches
• Error path: What happens when a key dependency fails — verify fallback/circuit breaker coverage
• Scale path: What happens at 10x expected load — verify scaling strategy holds

For each journey, verify:

• Every integration point between components is specified in both directions
• Data formats match (producer format = consumer expected format)
• Authentication/authorization is checked at every boundary
• Error handling is specified at every failure point

2. Risk Register

Create a risk register with probability x impact scoring:

#	Risk	Probability (1-5)	Impact (1-5)	Score	Mitigation	Owner

Include at minimum: technology risks, integration risks, operational risks, scale risks, security risks.