prd-mode

To create a product requirements document, you need a structured PRD covering problem statements, goals, user stories, and acceptance criteria. This skill automates structuring these elements into a standardized format saved as a markdown artifact.

A PRD for software features should include Overview, Goals, User Stories, Functional Requirements, Non-Goals, Technical Considerations, and Success Metrics. These mandatory sections ensure stakeholders have sufficient context for development decisions.

Identifying missing requirements and risks when writing a PRD requires an interactive clarification workflow. This skill uses an interrogation process to surface assumptions, risks, and unanswered questions, integrating the findings directly into the document.

Yes, this PRD generation process is specifically designed to guide junior developers. It walks them through problem definition, goal setting, and scope clarification to produce development-ready specifications for feature requests.

The best way to standardize PRD structure across features is to enforce mandatory sections and save outputs to a consistent file path. This skill auto-generates artifacts at a designated directory, ensuring uniform documentation.

The final PRD document is saved in markdown format. The auto-generated artifact is stored at a specific path, ensuring the structured product requirements are easily accessible for future development reference.