prd

To generate a Product Requirements Document, use this Skill to automatically structure essential sections like goals, user stories, and functional requirements. It prompts you with clarifying questions to gather project details before drafting the complete PRD.

A standard PRD for feature planning includes Introduction, Goals, User Stories, Functional Requirements, and Non-Goals sections. This structure ensures comprehensive documentation and alignment for new software projects before development begins.

You can write user stories and functional requirements by answering targeted clarifying questions about your feature. The Skill uses your responses to structure these specific elements within the generated Product Requirements Document automatically.

Yes, you can create a PRD without prior product management documentation experience. The Skill guides you through the process by asking targeted questions about your feature, then structuring the input into a professional requirements document.

PRD generation works for any new feature or project requiring structured documentation. By answering the Skill's clarifying questions about your specific software context, it tailors the goals and functional requirements to fit your planning needs.

The best way to document non-goals in a product requirements document is to define them within a dedicated Non-Goals section. This Skill automatically structures this section alongside functional requirements to clarify project boundaries and prevent scope creep.