PromptSharp › Prompt Library › Dev & Engineering › Ticket breakdown: split an epic into shippable, independently-testable slices
Ticket breakdown: split an epic into shippable, independently-testable slices
You have a vague epic and a sprint to fill. Break it into small tickets that each ship value and can be tested alone.
The prompt — copy and run it
You are a tech lead breaking a large piece of work into implementable tickets for my review. Produce: A) SLICE PLAN — the epic split into 4-8 tickets, each independently shippable and testable, ordered so early tickets de-risk later ones. B) PER-TICKET SPEC — for each: a one-line goal, the acceptance criteria, the main files/areas it touches, and a rough size (S/M/L). C) DEPENDENCIES — which tickets block which, and the one that should be spiked first if anything is uncertain. D) DEFERRABLE — what's explicitly out of scope for this pass, so scope doesn't quietly grow. Inputs: [THE EPIC / FEATURE] · [CONSTRAINTS + DEADLINE] · [SYSTEM IT TOUCHES] · [WHAT MUST SHIP FIRST] Rules: Do not invent requirements I didn't state — mark assumptions and open scope questions. Keep tickets genuinely independently testable, not artificial splits. Keep proprietary details out of consumer AI tools. This drafts the breakdown; the plan and estimates stay yours. Verify anything uncertain against the source before relying on it.
Why this prompt works
Epics stall as one giant unmergeable branch because they were never sliced; ordering independently-shippable tickets so early ones de-risk later ones, with explicit dependencies and an out-of-scope list, turns a vague epic into a sprint plan — and the assumptions-marked rule keeps invented requirements from silently expanding the work.
Want the daily version?
The PromptSharp Dev Brief delivers prompts like this every day. Honest status: sample stage — 50 waitlist signups start the free daily, and waitlist members see every issue first.
Frequently asked
When should I use this prompt?
You have a vague epic and a sprint to fill. Break it into small tickets that each ship value and can be tested alone.
Why does this prompt work?
Epics stall as one giant unmergeable branch because they were never sliced; ordering independently-shippable tickets so early ones de-risk later ones, with explicit dependencies and an out-of-scope list, turns a vague epic into a sprint plan — and the assumptions-marked rule keeps invented requirements from silently expanding the work.
What mistake does this prompt help you avoid?
{'code': 'PF02', 'note': 'Unsliceable epics — work is split into independently-testable, dependency-ordered tickets with an explicit out-of-scope list to stop creep.'}
Related Dev & Engineering prompts
Toil audit: find the hours a week your workflow is leaking
You suspect the week disappears into builds, reviews, and context switches. Audit it and get an automation plan with paybacks.…
Pre-review sweep: your own PR through a security-and-edge-case lens
The PR is 'done'. Run the pre-review sweep so human reviewers spend their attention on design — not on nits and the missed null ch…
All Dev & Engineering free prompts
The PromptSharp Dev Brief page — five full free prompts plus the ladder status.
PromptSharp Daily — free
The cross-vertical sampler: one sharp, copy-paste prompt each day, rotating across the roster. See what each vertical is like before you commit to one.
Double-opt-in. Unsubscribe anytime. No spam, ever.
Home · Prompt Library · Pricing · Archive · Privacy · Terms · Refunds
Finance · CPG · Marketing · Sales · Consulting & Strategy · Product Management · Dev & Engineering · C-suite · Law · Personal Finance · Career & Job Search · Focus & Productivity · Learning · Health & Fitness · Parenting