Draft an EPIC from a GitHub issue and open a PR for review. Use when triggered by a routine on `Issue opened` with label `ai:plan-epic`, or when a user asks to "draft an epic from issue #NNN". Non-interactive — proceeds on best interpretation and surfaces unresolved questions in the EPIC's §Open Questions section rather than blocking. The PR review loop resolves ambiguity. Does NOT write child SPECs — slice SPECs are drafted lazily by the `draft-spec` routine when the human files one `ai:plan` issue per slice after the EPIC PR is merged.
83
90%
Does it follow best practices?
Impact
87%
1.14xAverage score across 2 eval scenarios
Advisory
Suggest reviewing before use
Epic document structure and content
Template copied correctly
100%
100%
Every section filled
100%
100%
Status set to Draft
100%
100%
Slice table format
100%
100%
Slice status Not started
100%
100%
Measurable kill criteria
100%
100%
Cross-cutting decisions table
100%
100%
§Open Questions section present
100%
100%
Open Question structure
100%
100%
ADR cited in Why now
100%
100%
Slice ledger seeded
100%
100%
Epics index updated
100%
100%
No slice issues filed
100%
100%
Blocked-path triage: ADR status, scope, slice count
Proposed ADR blocked
100%
100%
Proposed ADR comment text
90%
100%
Proposed ADR label
25%
100%
Single-SPEC redirected
70%
100%
Single-SPEC comment text
40%
100%
Too-few slices blocked
100%
100%
Too-few slices label
25%
100%
No PR opened for blocked
0%
0%
Slack DM mentioned
0%
0%
Correct tool for GitHub ops
0%
0%
Does not draft any epic
100%
100%