Skip to content
Skills Library
Management & product · Planning

estimation

/estimation

Guides the user through risk-based task estimation using decomposition, three-point estimates, and PERT formula. ALWAYS trigger on "estimate", "how long will this take", "time to complete", "sizing", "scope this", "effort estimate", "how many hours", "story points", "project timeline", "when will this be done", "cost estimate", "level of effort". Use when sizing any work item, feature, or project.

Licence
MIT
Last repository change
03.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
1
HTML comments
1
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 03.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.
  • SKILL.md zawiera komentarze HTML (1). Nie widać ich w podglądzie Markdown, a model je czyta.

Scripts: scripts/estimate.sh

What it does and when to use it

Guides the user through risk-based task estimation using decomposition, three-point estimates, and PERT formula. ALWAYS trigger on "estimate", "how long will this take", "time to complete", "sizing", "scope this", "effort estimate", "how many hours", "story points", "project timeline", "when will this be done", "cost estimate", "level of effort". Use when sizing any work item, feature, or project.

Triggers from the description

estimatehow long will this taketime to completesizingscope thiseffort estimatehow many hoursstory points
Original author description

Guides the user through risk-based task estimation using decomposition, three-point estimates, and PERT formula. ALWAYS trigger on "estimate", "how long will this take", "time to complete", "sizing", "scope this", "effort estimate", "how many hours", "story points", "project timeline", "when will this be done", "cost estimate", "level of effort". Use when sizing any work item, feature, or project.

How it works

  1. Process
  2. Anti-Patterns
  3. Communication Template
  4. Validation Checklist
  5. When to Re-Estimate
  6. Script
  7. References
Original SKILL.md headings · 178 lines, 651 words
SKILL.md preview
---
name: estimation
description: >-
  Guides the user through risk-based task estimation using decomposition,
  three-point estimates, and PERT formula. ALWAYS trigger on "estimate",
  "how long will this take", "time to complete", "sizing", "scope this",
  "effort estimate", "how many hours", "story points", "project timeline",
  "when will this be done", "cost estimate", "level of effort".
  Use when sizing any work item, feature, or project.
---
<!-- Last reviewed: 2026-03 -->

# Estimation

## Process

### 1. Decompose Exhaustively

Break tasks until each piece is < 8 hours and estimatable with confidence.

```
Task: "Add user authentication"
  ├─ Database schema (2h)
  ├─ API endpoints (16h) → decompose further
  ├─ Password handling (8h)
  ├─ JWT tokens (19h) → decompose further
  ├─ Middleware (14h) → decompose further
  ├─ Testing (23h) → decompose further
  └─ Integration (22h) → decompose further
```

**Rule**: If you can't estimate confidently, decompose further.

### 2. Identify Unknowns

```yaml
unknowns:
  technical:  ["Never used bcrypt", "Don't know JWT refresh pattern"]
  domain:     ["Password rules unspecified", "SSO needed later?"]
  external:   ["DBA review has 2-day SLA"]
  resource:   ["Frontend dev availability uncertain"]
```

Every unknown adds risk. Quantify it.

### 3. Three-Point Estimate

For each atomic task:

| Estimate | Meaning |
|----------|---------|
| **Optimistic (O)** | Everything goes perfectly |
| **Realistic (R)** | Normal conditions, typical hiccups |
| **Pessimistic (P)** | Murphy's Law applies |

```
"Implement password hashing"
O: 1h  (copy existing pattern)
R: 3h  (read docs, test, handle edge cases)
P: 8h  (version issues, need alternatives)
```

**Rule**: If P > 3x R, decompose further.

### 4. Calculate PERT

```
Expected = (O + 4*R + P) / 6

Example: (1 + 4*3 + 8) / 6 = 3.5h
```

### 5. Apply Risk Buffers

| Risk Level | Multiplier | When |
|------------|------------|------|
| Low | 1.0-1.2x | Well-understood, clear requirements |
| Medium | 1.2-1.5x | Some unknowns, moderate complexity |
| High | 1.5-2.0x | New tech, unclear requirements |
| Critical | 2.0-3.0x | Multiple unknowns, bleeding-edge |

**Risk categories:**

| Category | Multiplier | Triggers |
|----------|------------|----------|
| Technical | 1.3-2.0x | New lang/framework, complex algorithms, perf requirements |
| Domain | 1.4-2.5x | Unclear requirements, regulatory, stakeholder disagreement |
| External | 1.5-3.0x | Third-party deps, vendor timelines, cross-team |
| Resource | 1.2-2.0x | Availability uncertain, skills gap, access issues |

### 6. Add Integration Buffer

Integration is where 50% of bugs live. Always add 20-30%.

```
Subtasks total: 40h
Integration buffer (25%): 10h
Final: 50h
```

---

## Anti-Patterns

| Anti-Pattern | Problem | Fix |
|-------------|---------|-----|
| "2 Hours" | "I have no idea" | Use three-point + PERT |
| Secret Padding | Destroys trust | State explicit buffer: "5h + 5h buffer" |
| Ignoring Integration | Underestimate 30-50% | Always add integration buffer |
| Forgetting Testing | "Done" != done | Include test time (often 1:1 with dev) |
| No Confidence Level | False precision | Use ranges: "45h +/- 5h" |

---

## Communication Template

```
[ESTIMATE] (+/-[UNCERTAINTY]) assuming [ASSUMPTIONS]

Breakdown:
- Component 1: Xh
- Component 2: Yh
- Integration: Zh

Confidence: [High/Medium/Low] (XX%)

Assumptions:
1. [Critical assumption]

Risks:
- [Risk]: [impact] / [mitigation]

Dependencies:
- [External dependency]

Unknowns:
- [Unknown] - [how to resolve]
```

---

## Validation Checklist

Before finalizing any estimate:

- [ ] Decomposed into atomic units (< 8h each)
- [ ] Every subtask has O/R/P estimates
- [ ] PERT formula applied
- [ ] All unknowns identified
- [ ] Risk buffers applied
- [ ] Integration buffer added (20-30%)
- [ ] Confidence level assigned
- [ ] Assumptions stated
- [ ] Risks identified with mitigations
- [ ] Dependencies noted
- [ ] Estimate is a range (+/- X)

---

## When to Re-Estimate

- Requirements change -- re-decompose affected components
- Unknown resolved -- update with actual findings
- Overrun > 20% -- stop and reassess remaining work
- Dependency changes -- adjust timeline
- Team changes -- different skills = different estimates

---

## Script

Run the interactive PERT estimation helper:

```bash
skills/estimation/scripts/estimate.sh
# or
./scripts/estimate.sh [--output filename]
```

---

## References

- `references/decomposition-examples.md` -- full worked examples
- `references/risk-analysis.md` -- risk assessment framework
- `references/communication-guide.md` -- stakeholder communication patterns
- `scripts/estimate.sh` -- interactive PERT estimation script
Files in this package (5)
  • SKILL.md 5 KB
  • references/communication-guide.md 2 KB
  • references/decomposition-examples.md 2 KB
  • references/risk-analysis.md 1 KB
  • scripts/estimate.sh 8 KB

Versions

RepositoryScoreLicence
This page · aj-geddes/unicorn-team100MIT
rpraharaj/forward-deployed-engineer100MIT
cdeust/zetetic-team-subagents90MIT

Database snapshot: 13.11.2026 · package version 261aa55a38f6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100estimate-calibrator
    Produces calibrated three-point PERT estimates (best/likely/worst) with confidence intervals, unknowns, and assumptions. Triggers on: "estimate this", "how long will this take", "effort estimate", "confidence interval", "story points", "t-shirt sizing". NOT for task…
  • 100create-estimation
    Create a three-point estimation when the user asks to estimate effort, scope a feature, size work, forecast timeline, or plan capacity for a project or feature
  • 100estimate
    Produces time and complexity estimates for features, tasks, or sprints using story points, t-shirt sizing, or day estimates. Use when the user asks for an estimate, wants to size a feature, or mentions estimation or planning poker.
  • 100project-sizing-guide
    Software project effort estimation assistant. Outputs three-point estimates (optimistic/most-likely/pessimistic values with confidence intervals), T-shirt sizes, or Function Point Analysis (FPA) counts. Triggered when users ask 'how long will this feature take,' need to assess…
  • 90ado-effort-estimation
    Estimate Azure Boards work with a mandatory clarifying-question gate and story-point guardrails. Trigger: when the user asks for effort sizing or story-point estimation.
  • 100doncheli-estimate
    Estimate effort, duration and cost using 4 complementary models (Function Points, Planning Poker AI, COCOMO, Historical). Activate when user mentions "estimate", "estimation", "effort", "how long", "cost", "story points", "sizing".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.