breakdown-feature-prd

To generate a product requirements document from an epic, provide the epic description and any constraints to the Skill. It acts as a senior product manager to produce a structured Markdown PRD with user stories, requirements, and acceptance criteria.

A production-ready PRD should include sections for Feature Name, Epic, Goal, Personas, User Stories, Functional and Non-Functional Requirements, Acceptance Criteria, and Out of Scope to guide cross-functional engineering and design work.

Yes, you can create user stories and acceptance criteria from a high-level feature description. The Skill processes your epic description to automatically generate these components and links them to the parent epic and strategic goals.

The best way to document out of scope items is to generate a structured PRD that explicitly includes an Out of Scope section. This clarifies release boundaries for cross-functional teams and prevents scope creep during development.

Yes, the Skill saves the generated PRD to a defined file path for project documentation. It produces an export-ready Markdown document at a standard location to facilitate team handoffs and documentation workflows.