requirements-grill

Structured product documentation is generated by running a six-layer grill workflow across Vision, Outcomes, Capabilities, Features, Evals, and Engineering Specs. It asks one question at a time with recommended answers to reduce ambiguity and extract testable requirements.

You can pause and resume product requirements sessions later, even across new chats, because the workflow stores conversation state in session files. This session persistence ensures your progress through the six-layer grill is never lost.

A three-stage WriteoutGate ensures requirements documentation is safely written by applying Preview, Label Audit, and Approval stages. The system only writes outputs to the docs directory after you explicitly review and approve the content.

The requirements extraction process supports optional web search escalation for time-sensitive fields like versions, model choices, eval methods, or benchmarks. It requests web verification when freshness is needed and labels web-derived values.

The best way to define product vision and outcomes step by step is through a grill workflow that prompts you one question at a time with recommended candidate answers. This staged approach keeps progress moving through the six documentation layers.