pm-prd

To generate a PRD from a feature description, provide the feature details along with optional inputs like target users, business goals, and product type. The system transforms these inputs into a delivery-ready markdown document covering background, goals, design modules, and acceptance criteria.

A product requirements document template includes sections for background, goals, detailed module design, non-functional requirements, analytics, schedule, risks, and appendices. It also features a 10-point quality self-check and Given-When-Then acceptance criteria.

You can create a B2B PRD using the same template, but the system applies product-type aware generation. It branches by B2C, B2B, internal tool, or platform, adjusting section emphasis and checks accordingly, and auto-detects the type from your inputs when possible.

Writing acceptance criteria using Given-When-Then is automated during feature decomposition. For each feature module, the system fills structured fields including description, user story, business rules, interaction flow, and exception handling, then generates the criteria directly in the PRD.

The best way to decompose features for product planning workflows is using three methods: user journey, role split, and CRUD for every core data object. This ensures each module captures description, user stories, business rules, and exception handling comprehensively.