matthew-a-carr/draft-epic
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
task.mdevals/scenario-1/
Draft an Epic for Multi-Tenant Support
Problem/Feature Description
Your team has been tasked with adding multi-tenant support to a SaaS platform. The initiative will span several engineering efforts: a new tenant data model, an auth layer update, per-tenant configuration, billing isolation, and an observability layer. The product manager has opened a GitHub issue (reproduced in inputs/issue.md) that captures the vision, scope, and initial slice ideas.
The strategic ADR governing this decision (inputs/adr-007-multi-tenancy.md) has already been reviewed and accepted. You have access to the project's existing epic template (inputs/_template.md) and the existing epics index (inputs/README.md), which shows EPIC-004 is the latest. The project structure also includes inputs/AGENTS.md and inputs/CONSTITUTION.md.
Your job is to draft a complete epic document for this initiative, following your team's standard process for epic planning. Write the epic as a file named docs/epics/EPIC-005-multi-tenant-support.md.
Output Specification
Produce the following files:
docs/epics/EPIC-005-multi-tenant-support.md— the complete epic document, filled from the templatedocs/epics/README.md— updated epic index with the new entry added
Do not file any slice issues. Do not produce any SPECs for individual slices.