spec

To generate a PRD from a feature idea, provide your concept to receive a structured document enforcing goals, non-goals, functional requirements, user stories, and acceptance criteria. This formalizes your initial concept into clear documentation.

Structuring user stories and acceptance criteria requires organizing them alongside functional and non-functional requirements within a PRD. This ensures clear scope boundaries and validation metrics for product teams.

Yes, you can update existing product requirements through iterative refinement. The skill supports clarifying questions and incremental updates to cross-reference existing docs, ensuring consistency as your project details evolve.

Yes, PRD generation works from a basic idea or feature request without predefined functional or non-functional requirements. It automatically formalizes these constraints, goals, and non-goals during the documentation workflow.

You need to define non-goals in a Product Requirements Document to establish strict scope boundaries and prevent feature creep. Setting non-goals explicitly clarifies what functionality is excluded from the current product requirements.