What problem does it solve? Writing feature-level PRDs that stay consistent with their parent epic is hard: personas, workflows, and requirement depth often drift from the epic's type. This Skill enforces that inheritance so Platform, Engine, and Domain features each get the right structure. ## Core Features & Use Cases - Type-Aware PRD Generation: Classifies the parent epic as Platform, Engine, or Domain and adapts personas, workflows, and UX depth accordingly. - Structured PRD Output: Produces a complete Markdown PRD with goal, personas, user stories, functional and non-functional requirements, acceptance criteria, and out-of-scope sections, saved to docs/product/{epic-name}/{feature-name}/prd.md. - Use Case: A product manager breaking an epic into features asks the assistant to draft a feature PRD; the Skill reads the parent epic, inherits its type, and produces a consistent, engineering-ready requirements document. ## Quick Start Write a feature PRD for the notifications feature under the messaging epic, inheriting the epic's type and saving it to the docs/product directory.