Planningprompt onlyintermediate

Epic Breakdown Loop

This loop helps decompose large epics into actionable user stories and development tasks. It guides the agent to analyze epic scope, generate well-defined stories with acceptance criteria, estimate effort for each story, and iterate until all stories are properly scoped and estimated for sprint planning readiness.

← all loops
agileplanningepicuser-storiesstory-splittingestimationsprint-preparation

Goal

Split epic into tasks

How to Run

Run this loop in your coding environment to break down an epic into estimated user stories. The agent will iteratively refine stories until they meet estimation and quality standards.

  1. 01

    Initialize Epic Breakdown

    Provide the epic details and any initial context

  2. 02

    Decompose Epic

    Agent generates user stories from the epic with clear acceptance criteria

  3. 03

    Review and Estimate

    Use 'story review' command to validate stories and estimates

  4. 04

    Iterate Until Ready

    Agent refines stories/estimates based on feedback until all are complete

Workflow Steps

  1. 01

    Parse provided epic for key deliverables, constraints, and success metrics

  2. 02

    Break epic into logical user stories following INVEST principles

  3. 03

    For each story, create clear 'Given/When/Then' acceptance scenarios

  4. 04

    Provide rough effort estimates (story points or time) for each story

  5. 05

    Run 'story review' command to validate completeness and accuracy

  6. 06

    Adjust stories, criteria, or estimates based on check results

Kickoff Prompt

Start the "Epic Breakdown Loop" loop.

Goal: Split epic into tasks
Max iterations: 10
Between iterations run: story review
Exit when: Stories estimated


Please provide the epic details you want to break down. Include title, description, business objectives, user personas involved, and any existing acceptance criteria or constraints. I will decompose this into user stories with acceptance criteria and effort estimates.

Self-pace this loop. After each iteration, run `story review` and evaluate the output, and only continue if the exit condition is not met (Stories estimated). Stop when the exit condition passes or 10 iterations are reached. Give a short status update each pass.

Guardrails

hardcoded
  • ·Never split a story more than 2 levels deep from the original epic
  • ·Ensure all generated stories have measurable acceptance criteria
  • ·Maintain traceability to the original epic requirements
  • ·Limit total story count to prevent overwhelming iteration cycles
  • ·Preserve business value focus across all decomposed tasks

Flow Diagram

rendering…

Related loops — Planning