vc-generate-spec

You generate a requirements doc by synthesizing research findings and user intent into plain-language SPEC artifacts, which bridge the gap between research and innovation phases for user review.

A product-discovery SPEC artifact is a plain-language requirements document outlining user needs, behavioral outcomes, and acceptance criteria, needed before moving from research to innovation and planning.

Yes, you can create a requirements document for a specific feature by providing a feature or task slug as input, such as 'new-feature-123', to generate the corresponding SPEC artifact.

To write a SPEC that captures user needs and behavioral outcomes, follow the provided workflow guidance detailing specific sections, rules, flow diagrams, and acceptance criteria for comprehensive documentation.

Generating a SPEC relies on synthesizing existing user intent and research findings, meaning you need preliminary research data available to transform into reviewable plain-language requirements.

A plain-language requirements document for product discovery includes sections for user needs, behavioral outcomes, flow diagrams, and acceptance criteria to ensure comprehensive task specification.