prd

To generate a product requirements document, provide a new feature concept and the skill will guide you through clarifying questions to produce a structured markdown PRD. It outputs sections for goals, user stories, and functional requirements suitable for development teams.

A standard PRD for feature planning includes Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics. These predefined sections ensure clear, actionable specifications for project initiation and development alignment.

Yes, you can gather user stories and functional requirements automatically by responding to the skill's guided questioning process. It asks clarifying questions about your feature to extract necessary details and outputs them into the final markdown document.

The best way to write actionable specifications is using a structured PRD format that explicitly defines goals, user stories, and acceptance criteria. This skill generates markdown documentation designed specifically to provide clarity to development teams and AI agents.

Creating a PRD requires no specific technical prerequisites or dependencies. You only need to provide a feature concept, and the skill will initiate the specification process by asking targeted questions to gather the necessary project details.

Defining non-goals when writing product requirements prevents scope creep by explicitly stating what the new feature will not deliver. The PRD includes a Non-Goals section to ensure development teams maintain focus on the core functional requirements.