igmarin Estimating Task Effort
Assign relative complexity estimates. Focus on comparison, not calendar time.
Quick Reference
- Input: Task list (from
generate-tasks) or PRD requirements. - Frameworks: Story points, t-shirt sizes, time ranges.
- Output: Each task annotated with estimate + confidence.
- Rule: Flag uncertainty - never fabricate precision.
HARD-GATE
DO NOT assign estimates you don't understand.
DO NOT default to "3 points" or "Medium" as a placeholder.
DO flag tasks needing further breakdown.
DO state confidence (high/medium/low) for every estimate.
Core Process
- Receive - task list or PRD requirements.
- Detect framework - ask user or infer from context (see Estimation Frameworks below).
- Analyze each task - scope, unknowns, whether it needs further breakdown.
- Assign - relative sizing, confidence level per task.
- Flag - low-confidence tasks (recommend spike), oversized tasks (recommend split).
- Output - annotated task list.
Estimation Frameworks
| Framework | Scale | Use When |
|---|---|---|
| Story Points (Fibonacci) | 1 Trivial · 2 Small · 3 Medium · 5 Large · 8 Very Large · 13 Epic (→ split) | Agile/Scrum teams focusing on relative complexity |
| T-Shirt Sizes | XS · S · M · L · XL (→ split) | High-level roadmap sizing or stakeholder-facing discussions |
| Time Ranges | <1d · 1-2d · 3-5d · 1-2wk · 2+wk (→ split) | Fixed-bid projects requiring calendar anchors |
Mixing frameworks: Never mix frameworks within a single estimation table. If the user switches frameworks mid-session, re-estimate the full table.
Output Style
- Framework - state which framework was used and why.
- Estimation table -
| ID | Task | Estimate | Confidence | Notes | - Flagged items - tasks needing spikes or splits, with reasoning.
- Summary - total estimate, confidence distribution, callouts.
- English only unless user requests otherwise.
Integration
| Skill | When to chain |
|---|---|
| generate-tasks | Estimate tasks immediately after generation |
| identify-risks | After estimation, assess dependency and uncertainty risks |
| plan-sprint | Select tickets based on capacity vs estimates |
Worked example: assets/example-session.md.