narrative-doc

Draft an iterative technical proposal by building each section—background, goals, proposal, open questions, and appendices—sequentially while pausing for human sign-off before moving forward. This section-by-section workflow ensures structured stakeholder review at every step.

Design rationale documentation explains the technical decisions and migration plans behind a system change in a stakeholder-friendly narrative format. You need it when you must justify a design direction or architectural shift without jumping straight into a rigid specification.

Yes, you can insert Mermaid diagrams into a narrative proposal document to clarify complex technical concepts. The drafting workflow automatically adds Mermaid visualizations where they improve understanding for stakeholders reviewing the design rationale.

Ground a technical proposal in codebase context by feeding prior research and decision briefs into the drafting process. The workflow uses this contextual grounding to ensure the narrative proposal accurately reflects the actual system architecture and terminology.

Yes, narrative proposal drafting requires a living terminology table to maintain clarity across all sections. This terminology tracking ensures consistent vocabulary usage throughout the background, goals, proposal, open questions, and appendices sections during human review.