Creating a Product Requirements Document for a New Epic in the Style of an Expert Product Manager

1. Provide the epic idea as a general description. You can also add your initial view of the target users using the context template (Epic Idea and Target Users). 2. Example user request: "I want a requirements document for a new epic that adds an in-app notification system for users of our platform, and the target users are team managers." 3. Answer the clarifying questions the agent asks if the information is not sufficient to define aspects of the epic. 4. The agent creates a complete PRD with the eight specified sections and saves it to the path /docs/ways-of-work/plan/{epic-name}/epic.md. 5. Review and edit the resulting document, then use it as input for preparing the epic's technical architecture specification.

The skill does not require external tools or accounts; it consists of text instructions only. The agent must be able to write files in the project repository to save the document to the path /docs/ways-of-work/plan/{epic-name}/epic.md; otherwise, the content can be displayed as text and copied manually. The quality of the document depends on the clarity of the idea provided and the answers to the clarifying questions, and the impact and business value estimates are approximate and require human review. The skill does not create the technical architecture specification itself. The source is licensed under the MIT License from GitHub.