# 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.

- Topic: Projects & Operations
- Framework: Few-Shot
- Level: Standard
- Tags: Analyze, Code, Fill-in Template
- Source: https://www.thinkwithprompt.com/prompts/estimate-an-engineering-task-with-an-honest-range

## Prompt

```text
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.
```

## 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

Free to copy and use. From ThinkWithPrompt (https://www.thinkwithprompt.com/), a library of 2,663 curated AI prompts.