prd-v01-problem-framing

To frame a vague product idea, you supply the initial concept and the Skill transforms it into an evidence-anchored problem statement. It extracts pain dimensions, quantifies costs, and structures the output with CFD IDs for validation.

The best way to draft a Why section for a PRD v0.1 is using structured problem tables and gap assessments. This process validates missing evidence and produces a ready-to-use problem statement template with references to guidance assets.

You validate market opportunities by running a gap assessment on your initial product idea. The Skill identifies missing evidence, extracts customer insights, and quantifies pain dimensions to ensure your market opportunity is anchored by data.

Yes, you can use CFD entries to structure customer insights for product research. The Skill generates structured problem tables linked with CFD IDs, standardizing your research outputs into spark-ready artifacts for PRD handoff.

You do not need existing customer research to generate a problem-statement template. The Skill takes a vague product idea or trigger phrase, performs gap assessments, and drafts the problem statement by extracting and anchoring available evidence.