product-requirements

Describe your feature request, and the Skill gathers context through interactive dialogue, scores your requirements across business value, functional specs, UX, and technical constraints using a 100-point system, then generates and saves a polished PRD to docs/{feature-name}-prd.md once it reaches 90+ quality score.

The quality score evaluates requirements across five dimensions: business value, functional requirements, user experience, technical constraints, and scope definition. A 90+ score triggers PRD generation; below 90, the Skill asks targeted clarification questions to fill gaps.

Yes. The Skill collects project context from your README, package manifests, and existing assets, then applies the same iterative refinement and quality assessment process to generate professional requirements documentation aligned with your current stack.

If your requirements score below 90, the Skill asks 2–3 focused clarification questions per round targeting the lowest-scoring dimensions, refining your input until the quality threshold is met and a complete PRD is generated.

The finalized PRD is saved to docs/{feature-name}-prd.md in your project, creating a persistent, version-controlled requirements artifact for stakeholders and development teams.

No. The Skill guides you through structured requirement gathering and provides the quality framework; you supply the feature idea and context, and iterative feedback helps shape professional-grade requirements regardless of prior PRD experience.