What problem does it solve? Writing Epic-level PRDs often produces bloated, inconsistent documents that mix platform, engine, and domain concerns, making them unreliable as a source of truth for engineering teams. ## Core Features & Use Cases - Type-Aware Authoring: Classifies each epic as Platform, Engine, or Domain before drafting, enforcing the correct personas and Section 4 structure (journeys vs. Domain Integration Contract). - Structured PRD Generation: Produces a complete Epic PRD in Markdown saved to docs/product/{epic-name}/epic.md with capped requirement counts (≤15 functional, ≤8 non-functional). - Severity-Graded Review: Audits existing epics against a checklist covering classification, journeys, requirements, metrics, scope, and consistency, returning findings labeled Critical, High, Medium, Low, or Act Now. - Use Case: A product manager planning a scheduling SaaS asks for an epic PRD; the skill first confirms splitting it into a platform epic, a solver engine epic, and a school domain epic, then drafts each with the correct structure. ## Quick Start Ask the assistant to create an Epic PRD for your product idea, or to review an existing epic document for structural and consistency issues.