prd

A PRD structures feature ideas into actionable requirements. This skill generates a comprehensive PRD with Introduction, Goals, User Stories, Functional Requirements, and Non-Goals sections from your feature description, then saves it as a standardized markdown file for team handoff.

A structured PRD contains Introduction, Goals, User Stories with acceptance criteria, Functional Requirements, Non-Goals, and Open Questions sections. This skill auto-generates each section from your feature description and incorporates clarifying questions to resolve ambiguities before development starts.

Clarifying questions identify and resolve ambiguities in your feature description before the PRD is finalized. This ensures the requirements are complete and unambiguous, reducing misalignment between product and development teams.

Yes. This skill applies reusable PRD templates with consistent sections and formatting, ensuring quality and alignment across all your products. Each output saves to a standardized filename for easy integration into project workflows.

Generate a PRD during feature planning, project kickoff, or whenever you need to clarify requirements before handoff to development. It's most valuable early in the cycle to prevent scope creep and misalignment.

The PRD is automatically saved to tasks/prd-[feature-name].md, using your feature name in the filename for easy tracking and integration into your project management workflow.