niwashi-02-research

A narrative specification coordinates technical analysis, audience insights, narrative arc, and visual language into a single document. It ensures cross-stream consistency and captures pattern lineage before moving into wireframe planning and user review.

You validate audience research and technical analysis by running cross-stream consistency checks before final synthesis. This structured validation ensures the narrative specification accurately captures all research streams before user approval.

The best way to structure visual language and narrative arc research is running parallel technical and audience streams in phase A, followed by sequential streams in phase B. This structured approach feeds unified outputs into a single narrative specification document.

Yes, an existing narrative brief is required to generate a narrative specification document. The process triggers when a brief exists and requires four research streams to produce a synthesis suitable for wireframe planning and user approval.

Yes, narrative specifications are explicitly designed for wireframe planning and visual language design. The final document captures cross-stream validations and pattern lineage, creating a structured foundation directly suitable for downstream wireframe development.