Split a Large Jira Epic Into Thin Vertical Stories
Slice an epic so each story delivers something usable.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Split this epic into stories. Epic summary and description: [EPIC_TEXT]. Users and the outcome they need: [USERS_AND_OUTCOME]. Technical layers involved: [LAYERS]. Earliest date we want something in front of users: [FIRST_RELEASE_DATE]. Propose a first slice a real user could use end to end, even if plain, then further slices that add capability, using at least three slicing patterns where they fit: by workflow step, user type, data variation, rule complexity, interface depth, and quality attribute such as performance. Show your reasoning for the first slice, since the team will argue about it: what a user can do after it ships, how we would know it worked (one measure or observation), and which parts of the system it touches. Check each later slice against three tests: can it ship alone, does it change something the user notices, could we stop after it without wasting earlier work? Rename any slice that fails the first test, around user value. Return a table with Order, Story summary, User-visible result, Left out and Depends on, a map of slices that can run in parallel, and one plain-language sentence per slice for a non-technical stakeholder. Leftover technical work (a database change, an API contract, a migration) belongs inside the first user-facing story if possible, otherwise in a small enabling task or in the definition of done. Finish with the three questions for the product owner that remove the most uncertainty, and how to record the split in Jira: parent epic, child stories, and links showing order [VERIFY link types]. Do not invent details about our system.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.