write-epiclisted

## What this skill does Produces a complete epic definition following Atlassian agile guidance. An epic captures a large initiative that is too big for a single sprint and must be decomposed into user stories. This skill writes the epic statement, defines in-scope and out-of-scope boundaries, identifies success metrics, and drafts an initial story map to guide decomposition. **Reference:** Atlassian — [User stories with examples and a template](https://www.atlassian.com/agile/project-management/user-stories) ## When to use it - User asks to "write an epic" or "define an initiative" for a feature area or product goal. - User has a large, multi-sprint requirement and needs to frame it before decomposing it into stories. - User wants to communicate a roadmap item to stakeholders before stories are written. - User is decomposing an epic and needs the parent definition to stay aligned. ## Key concepts ### Epic vs. user story | | Epic | User Story | | --- | --- | --- | | **Size** | Multiple sprints | Fits in one sprint | | **Granularity** | Strategic intent | Specific capability | | **Audience** | Stakeholders + team | Team | | **Detail** | Goal + boundaries + metrics | Action + benefit + acceptance criteria | | **Completeness** | Done when all child stories are done | Done when acceptance criteria pass | ### Epic goal statement An epic does not use the Connextra ("As a … I want … so that …") template directly — it uses a **goal statement** that captures the initiative and