SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsestimate-tasks

estimate-tasks

General & other

View repository

Updated 10-15 22:16

About this skill

Estimating Task Effort

Assign relative complexity estimates. Focus on comparison, not calendar time.

Quick Reference

  • Input: A draft work-item list from plan-tickets 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

  1. Receive - task list or PRD requirements.
  2. Detect framework - ask user or infer from context (see Estimation Frameworks below).
  3. Analyze each task - scope, unknowns, whether it needs further breakdown.
  4. Assign - relative sizing, confidence level per task.
  5. Flag - low-confidence tasks (recommend spike), oversized tasks (recommend split).
  6. 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

  1. Framework - state which framework was used and why.
  2. Estimation table - | ID | Task | Estimate | Confidence | Notes |
  3. Flagged items - tasks needing spikes or splits, with reasoning.
  4. Summary - total estimate, confidence distribution, callouts.
  5. English only unless user requests otherwise.

Integration

Skill When to chain
plan-tickets Estimate draft work items after decomposition
identify-risks After estimation, assess dependency and uncertainty risks
plan-sprint Select tickets based on capacity vs estimates

Worked example: assets/example-session.md.