doncheli/don-cheli-sdd / .agent/skills/doncheli-estimate
doncheli-estimate
VerifiedEstimate 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".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
SKILL.md
View on GitHub---
name: doncheli-estimate
description: 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".
---
# Don Cheli: Estimation Engine
## Instructions
1. Read the feature, story or task description
2. Run all 4 estimation models independently (treat each as a separate agent):
- **Function Points**: count inputs, outputs, queries, files, interfaces; apply complexity weights
- **Planning Poker AI**: 3 independent agents guess simultaneously (pessimist, realist, optimist), then reconcile using Delphi method
- **COCOMO II**: classify project size (Organic / Semi-detached / Embedded), apply effort equation
- **Historical**: look for comparable past tasks in `.dc/hallazgos.md` and `docs/`; extrapolate velocity
3. Compute the consolidated estimate with 90% confidence interval
4. Flag hidden risks that inflate variance
## Output Format
```
## Estimation: <feature name>
| Model | Estimate | Unit | Confidence |
|------------------|------------|------------|------------|
| Function Points | X | hours | medium |
| Planning Poker | X–Y | story pts | high |
| COCOMO II | X | person-days| medium |
| Historical | X | days | low/med |
**Consolidated:** X–Y days (90% CI)
**Key assumptions:** …
**Top 3 risks that increase variance:** …
```
## Quality Gate
- All 4 models must be executed; do not skip any
- If Historical has no comparable baseline, mark as N/A and explain
- If Planning Poker spread > 2x, escalate: ask the user to clarify scope before finalizing
## Do not use this skill when
- The task is trivially small (< 1 hour) — just state it directly
- The user is asking for a rough gut-feel order of magnitude; use a one-liner instead
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |