vc-generate-spec

To generate a product specification from user research, you provide your research findings and user intent details. The skill processes these inputs to output a structured, reviewer-ready SPEC document saved as a markdown file in your active task folder.

A plain-language product discovery SPEC requires canonical sections including Summary, User Stories, Behavioral Outcomes, Flow Diagram, Acceptance Criteria, Out Of Scope, Constraints, Open Questions, and Background/Research Findings to ensure alignment.

You turn user intent into testable acceptance criteria by feeding your research insights into this skill, which translates them into structured behavioral outcomes and formal requirements aligned with canonical SPEC contract rules before planning.

You can create a formal requirements document directly from research without dependencies, as the skill operates standalone. You only need your research data and user intent details ready to input for processing.

The best way to document product discovery findings before planning is generating a formal SPEC document. This artifact captures user goals, research insights, and rationale, ensuring alignment and testable criteria before moving to the PLAN phase.

You should not use a standard template because it may lack enforced canonical SPEC contract rules. This skill ensures structured alignment and saves outputs automatically in a phase-driven workflow format, preventing missing critical sections.