product-requirements

To write a PRD from a feature brief, provide your initial requirements to start an interactive dialogue. The assistant gathers context, applies a 100-point quality score, and iteratively refines the document until it reaches a 90+ passing score.

Interactive requirements gathering works by prompting targeted clarifications about constraints and acceptance criteria. This mechanism ensures scattered user needs are transformed into organized, testable product requirements documents through iterative dialogue.

Yes, you can generate a PRD without upfront technical details. The assistant elicits necessary context, business value, and technical constraints during the interactive dialogue, prompting for clarifications until the requirements meet the quality threshold.

The 100-point quality score is an assessment mechanism evaluating business value, functional requirements, UX, technical constraints, and scope. It measures PRD completeness, triggering targeted clarifications until the document achieves a 90+ passing score.

Generated PRD files are saved directly to your project directory at `.claude/specs/prd/{feature-name}.md`. This output includes an executive summary, user stories, and technical details formatted as a professional markdown document.

The best way to turn scattered user needs into testable acceptance criteria is using an iterative quality assessment workflow. This approach evaluates functional requirements and scope, prompting for targeted clarifications to refine constraints into a professional PRD.