What problem does it solve?
Converts high-level epics and brief feature requests into a single, structured Product Requirements Document (PRD) that engineering and product teams can use as the source of truth, reducing ambiguity and back-and-forth during planning and implementation.
Core Features & Use Cases
- Structured PRD Generation: Produces a complete Markdown PRD including feature name, links to Epic, goal (problem/solution/impact), user personas, user stories, functional and non-functional requirements, acceptance criteria, and out-of-scope items.
- Clarification and Validation: Prompts for missing information and refines requirements through follow-up questions to ensure readiness for engineering handoff.
- Use Case: A product manager provides an Epic and a short feature description and receives a ready-to-use PRD saved into the repository path for documentation and planning.
Quick Start
Use this prompt to generate a complete PRD from an epic and feature description, asking clarifying questions if information is missing.