write-prd

To generate a product requirements document, the Skill gathers initial context and drafts a structured PRD including the problem statement, proposed solution, user stories, and acceptance criteria. It structures the document according to a defined template and saves it in the project documentation directory.

A structured PRD includes a problem statement, proposed solution, user stories, and acceptance criteria. This ensures clear communication and a shared understanding of product definition between product, development, and design teams.

Writing user stories and acceptance criteria is handled by the Skill during the document generation process. It drafts these elements within the PRD template and requires your iterative review and approval before finalizing the product definition.

Yes, you can review and refine the PRD before it is saved. The Skill uses an iterative review process that requires user approval of the drafted product requirements document before finalizing and saving it in the project's documentation directory.

Yes, the PRD generation process works without external dependencies. The Skill operates independently using its internal references component to gather context, research project documentation, and structure the final product requirements document.

The best way to define product requirements for team communication is using an iterative PRD generation process. It automates creating a comprehensive document with problem statements, solutions, user stories, and acceptance criteria to ensure shared understanding across teams.