Estimate an engineering task with an honest range
Breaks down a task, surfaces hidden work and unknowns, and gives a best/likely/worst estimate you can defend to your team.
The prompt
Help me estimate an engineering task honestly.
Task: [WHAT NEEDS TO BE BUILT OR CHANGED]
What I know about the codebase here: [FAMILIARITY, CODE QUALITY, TEST COVERAGE]
Dependencies on others: [OTHER TEAMS, REVIEWS, DESIGN, APPROVALS, VENDORS]
My gut estimate: [e.g. "3 days"]
Who is asking and why: [e.g. "PM planning the quarter", "manager committing to a customer date"]
Estimate format we use: [hours / days / story points / T-shirt sizes]
Steps:
1. Break the task into work items, including the ones people forget: tests, code review cycles, migrations, docs, deployment, monitoring, QA fixes, and coordination.
2. Label each item: known, familiar-but-uncertain, or unknown. Unknowns get a time-boxed investigation item.
3. Estimate each as best case / likely / worst case.
4. Compare the total with my gut estimate and explain the gap.
Return:
- The breakdown table (item, type, best, likely, worst, notes).
- A summary range and the confidence level I can state.
- The top 3 assumptions that, if wrong, blow up the estimate.
- What I could cut or defer to hit a tighter date.
- A 3-sentence message to the person asking that gives the range and its assumptions without sounding evasive.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- WHAT NEEDS TO BE BUILT OR CHANGED
- FAMILIARITY, CODE QUALITY, TEST COVERAGE
- OTHER TEAMS, REVIEWS, DESIGN, APPROVALS, VENDORS
- e.g. "3 days"
- hours / days / story points / T-shirt sizes
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Design a cycle counting program to fix inventory accuracyA risk-based cycle count schedule, variance investigation steps, and accuracy targets that make system stock match the shelf.
- Turn business insights into an action plan with owners and deadlinesConverts findings from an analysis, review, or workshop into a prioritized action plan with owners, deadlines, and success measures.
- Map my process step by step and find the wasteBreaks a workflow into steps and flags waste: duplicate work, unnecessary handoffs, waiting, rework, and steps that add no customer value.
- Find unnecessary approvals in a workflow and simplify sign-offsReviews every approval in a workflow, flags the ones that add delay without reducing risk, and proposes a leaner sign-off design with thresholds.