prd

A Product Requirements Document (PRD) outlines the overview, goals, and user stories for a new software feature. You need a PRD during project planning to ensure requirement clarity and comprehensive feature documentation before development begins.

To generate a PRD, trigger the skill with a command like 'create a prd for my new feature'. The process involves question-answering for requirement clarification and automatically produces a well-structured, markdown-formatted feature documentation file.

Yes, this PRD generation process includes user clarification steps. It will ask you targeted questions to gather comprehensive requirements and ensure your project management documentation is clear and complete even if initial goals are vague.

The best way to structure feature documentation is using a standardized PRD format. This approach outputs a markdown file containing dedicated sections for the project overview, goals, user stories, and specific product requirements.

Yes, this approach is designed for both project managers and developers needing to document feature requirements. It streamlines project management by translating requirement gathering into structured markdown formatted product requirements documents.