to-epic

Synthesize the current conversation into one epic — a parent issue whose body is the full PRD — plus tracer-bullet sub-issues under it, each declaring its blocking edges. Do not interview the user; synthesize what you already know.

Tracker-agnostic: the epic, its children, and blocking edges are the same everywhere. How they are stored (GitHub sub-issues, Linear parent/sub-issues, local markdown, Jira, ...) comes from the repo's configured tracker docs. If none are configured, ask which tracker and how parent/child + blocking are expressed before publishing.

Process

1. Orient

Explore the repo if you have not already. Use the project's domain glossary throughout, and respect ADRs in the area you are touching.

Sketch the seams at which you will test the feature. Prefer existing seams; prefer the highest seam; fewer seams is better (ideal: one). Confirm the seams with the user.

Done when: seams are listed and the user has confirmed them.

2. Draft the epic

Write the epic body using the template in epic-template.md. Keep it in the conversation — do not publish yet.