prd

To write a product requirements document that defines the end state, this Skill guides you through targeted clarifying questions about problems, users, scope, risks, and dependencies to generate a structured Markdown PRD file.

A PRD for feature planning should include structured sections for the problem statement, scope, constraints, risks, and acceptance criteria to ensure development clarity and avoid ambiguity.

Yes, you can use this PRD template for migrations and refactors because it provides a reusable Markdown format that captures rationale and sets success criteria across various feature planning scenarios.

The best way to document feature requirements and acceptance criteria is to automate the process with targeted clarifying questions that output a reproducible Markdown file named prd-<feature-name>.md in your project root.

To generate a Markdown PRD file in your project root, load the Skill, describe your feature, and it will automatically create a reproducible document named prd-<feature-name>.md with consistent sections.