What problem does it solve? Writing a PRD for a Notion epic by hand means copying epic metadata, task lists, and sprint details into a document and then drafting requirements from scratch. This Skill automates that by pulling the epic hierarchy directly from Notion and producing a structured PRD markdown file in your repository. ## Core Features & Use Cases - Notion Epic Resolution: Resolve an epic from an explicit ID (e.g., GP-1014), the current git branch context, or an interactive picker fed by the Notion sprint hierarchy. - Pre-filled PRD Template: Generates a markdown file with metadata table, tasks table (ID, status, assignee, category), sprint info, and a Notion link, plus configurable custom sections. - Optional Planning Interview: Delegates to the OMC Planner agent to interview you about overview, requirements, affected services, technical design, and acceptance criteria, then fills the PRD sections. - Existing File Handling: Detects an existing PRD for the epic and offers Update (refresh metadata/tasks only), Overwrite, or Cancel. - Use Case: A product manager starts a sprint, runs the skill on epic GP-1014, answers a short planning interview, and commits a complete PRD to docs/prd/GP-1014-user-authentication.md. ## Quick Start Ask the assistant to generate a PRD for Notion epic GP-1014 and choose whether to run the planning interview when prompted.