What problem does it solve? Turning an approved strategic bet (an OKR key result or PRD section) into a well-formed Epic is often ad hoc: scope creeps, success criteria stay vague, and the link back to strategy gets lost. This Skill enforces a governed drafting process where every Epic is a versioned markdown artefact with mandatory strategic linkage. ## Core Features & Use Cases - Template-driven drafting: Uses the project's EPIC.template.md verbatim to produce 30-Epics/EPIC-NN-<slug>.md with all required sections filled. - Mandatory strategic linkage: Requires frontmatter okr: or prd_section: referencing the source document, and aborts if linkage cannot be established. - Automatic numbering: Globs existing EPIC-*.md files to compute the next free EPIC-NN, preventing collisions. - Use Case: After approving a Q3 OKR, ask the assistant to draft an Epic from KR2; it reads the OKR file, applies the template, outlines 3-7 candidate Features, and shows the planned file tree for approval before writing. ## Quick Start Ask the assistant to draft an epic from a specific OKR or PRD file, for example: draft an epic from _00-Project-Management/00-Strategy/OKR-2025-Q3.md key result 2.