PromptSharp › Daily briefs › Dev & Engineering › July 22, 2026

Dev & Engineering prompt of the day

July 22, 2026 · for Software engineers, tech leads, engineering managers. One sharp, copy-paste prompt — free, every weekday.

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.

What changed for Dev & Engineering

How to run “Ticket breakdown: split an epic into shippable, independently-testable slices”, step by step

The situation this prompt is built for: You have a vague epic and a sprint to fill. Break it into small tickets that each ship value and can be tested alone. Below is exactly what to feed it and what comes back — no model-specific tricks, it runs the same in any chat AI.

What each placeholder does

Demo profile for the example fills: a senior backend engineer on a 12-person product team, working in GitHub, CI, and an AI coding assistant. Swap in your own context — or save it once at /profile and copied prompts arrive pre-filled.

• [THE EPIC / FEATURE] — this is the input the whole output quality hangs on. Each part narrows the answer: the epic; feature. Demo fill: your own the epic / feature — one or two concrete lines beats a paragraph of vague context. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.
• [CONSTRAINTS + DEADLINE] — this is the input the whole output quality hangs on. Each part narrows the answer: constraints; deadline. Demo fill: only the constraints that are genuinely fixed — e.g. “two-reviewer PR policy, no deploys on Fridays”. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.
• [SYSTEM IT TOUCHES] — this is the input the whole output quality hangs on. Demo fill: your own system it touches — one or two concrete lines beats a paragraph of vague context. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.
• [WHAT MUST SHIP FIRST] — this is the input the whole output quality hangs on. Demo fill: your own what must ship first — one or two concrete lines beats a paragraph of vague context. Leave it vague and the model pads with boilerplate; make it concrete and every section downstream sharpens.

Why this structure 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.

On Pro, pro personalization stores your ticket format, sizing scale, and codebase map so breakdowns match how your team actually plans.

When to use it — and when not to

Reach for it when

• You have a vague epic and a sprint to fill. Break it into small tickets that each ship value and can be tested alone.
• You can actually supply the inputs it asks for ([THE EPIC / FEATURE] and 3 more) — this prompt is an amplifier for real context, not a substitute for it.
• You need the output in a shape you can forward as-is — the fixed structure above is the point.

Skip it when

• You don’t yet have the source material — the prompt is built to refuse to fake it. Its own guardrail: “Do not invent requirements I didn't state — mark assumptions and open scope questions.” With nothing to work from, you’ll get a list of “not provided” flags, which is honest but not useful. Collect the inputs first.
• The classic misuse this prompt was tuned against: Unsliceable epics — work is split into independently-testable, dependency-ordered tickets with an explicit out-of-scope list to stop creep.
• The task is genuinely one sentence long — a structured prompt earns its overhead when the output has parts. For quick one-off questions, just ask.

Adapting today’s prompt for adjacent roles

“Ticket breakdown: split an epic into shippable, independently-testable slices” sits in the Dev Productivity lane of the dev & engineering pool. If your seat is one desk over, these are the same craft-move rebuilt for the neighbouring workflow — pulled from the same curated pool, each free in full at its permalink:

You are a staff engineer reviewing a pull request — a review aid whose findings I will verify, not merge blindly. Produce: A) RISK SUMMARY — a one-line verdict (safe /…

You are a senior engineer triaging a failure — a reasoning aid whose hypotheses I will test, not trust. Produce: A) READ — a plain-English restatement of what the error…

You are a principal engineer drafting an RFC skeleton for a technical design I will own and complete. Produce: A) PROBLEM + CONSTRAINTS — the problem in two sentences…

Common failure modes (and the fixes)

• Failure: letting the model drift past the prompt’s own guardrail — “Do not invent requirements I didn't state — mark assumptions and open scope questions.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Keep tickets genuinely independently testable, not artificial splits.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: letting the model drift past the prompt’s own guardrail — “Keep proprietary details out of consumer AI tools.” Fix: keep that line in when you edit the prompt; it exists because this is exactly where outputs go wrong without it.
• Failure: filling [THE EPIC / FEATURE] with a vague summary. The output can only be as specific as this input — generic context in, generic deliverable out. Fix: paste raw specifics (real names, real numbers, real constraints), then trim the model’s output, not your input.
• Failure the prompt was tuned against: Unsliceable epics — work is split into independently-testable, dependency-ordered tickets with an explicit out-of-scope list to stop creep.
• Failure: accepting the first pass. Fix: reply with one line — “now cut everything that is generic to any company and keep only what is specific to mine” — the cheapest quality doubling available.

Where AI is landing for software engineers right now

Context for today’s prompt, from the same screened sources the daily brief reads. Our read, with sources linked — the pattern across items like these is consistent: the professionals getting leverage from AI are the ones feeding it real working context, which is exactly the muscle today’s prompt trains.

• OpenAI Hacks Hugging Face, What Happened, Alignment and Paper Clips (rss) — OpenAI accidentally hacked Hugging Face, but the takeaways are more encouraging than people realize.

Quick answers

Is “Ticket breakdown: split an epic into shippable, independently-testable slices” free to use?

Yes — every weekday issue of the PromptSharp Dev Brief publishes one full pool prompt free on the web, and it stays free in the archive. Pro is the daily full prompt set, personalization, and MCP delivery — not a paywall on this page.

Which AI model does this prompt work with?

Any of them. Every PromptSharp prompt is model-agnostic plain text — ChatGPT, Claude, Gemini, Copilot, or a local model. No plugins, no custom GPTs; paste and run.

How is the dev & engineering prompt of the day chosen?

Deterministic rotation over the curated dev & engineering pool — currently 10 prompts across 5 sections — the same single source the paid brief reads. Same date, same prompt: the archive never silently changes under you.

What goes in the [BRACKETED] placeholders?

Your context — the walkthrough above covers each one. The short rule: the more concrete the fill (real names, numbers, constraints), the sharper the output. Save your details once at /profile and web copies arrive pre-filled.

How do I get this in my inbox instead?

The capture form above — PromptSharp Dev Brief status is honest: live briefs send every weekday; pre-launch verticals email their free list the day the email edition starts.

More daily AI prompt briefs

The same free weekday format, tuned to other crafts:

• PromptSharp Finance — for Investment banking, sales & trading, equity research, FP&A
• PromptSharp CPG Brief — for Brand managers, category managers, insights & shopper teams
• PromptSharp Marketing Brief — for Brand and growth marketers, agency strategists, content leads
• PromptSharp Sales Brief — for AEs, SDRs, sales leaders, RevOps
• PromptSharp Consulting Brief — for Management consultants, corporate strategy, biz-ops
• PromptSharp Product Brief — for PMs, product ops, founders wearing the PM hat
• PromptSharp Vibe Coding Brief — for Founders, PMs, designers, analysts — anyone building real software with AI without an engineering background
• PromptSharp C-suite Brief — for CEOs, CFOs, CMOs, CTOs, COOs and their chiefs of staff
• PromptSharp Law Brief — for Solo & small-firm attorneys, litigation & transactional associates, in-house counsel
• PromptSharp Personal Finance Brief — for Anyone running their own money — budgets, investing, taxes, and the rent-vs-buy / home-buying decisions that dwarf every other line item
• PromptSharp Career Brief — for Job seekers, career changers, anyone negotiating an offer
• PromptSharp Focus Brief — for Anyone who wants external structure for deep work — ADHD-friendly by design
• PromptSharp Learning Brief — for Self-directed learners — languages, skills, certifications, exam prep
• PromptSharp Health & Fitness Brief — for Anyone training, eating better, or building durable habits
• PromptSharp Travel Brief — for Trip planners — itineraries, deals, points, family logistics
• PromptSharp Students — for College students (undergrad + grad) — study, research, essays with integrity, exam prep, applications
• PromptSharp Trading — for Self-directed retail traders and active investors — risk and position-sizing thinking, regime awareness, journal review, bias-checking, earnings prep. Your own account, your own process.

← 2026-07-20 · All Dev & Engineering issues