# Estimate Agile Tasks With Story Points

Teams need consistent estimates for sprint planning and roadmaps. This skill guides story points, planning poker, sizing, risks, and task breakdowns.

## Install

```bash
npx skillstore add supercent-io/task-estimation
```

## Metadata

- Status: approved
- Slug: supercent-io-task-estimation
- Skillstore revision: r1
- Version status: missing
- Tree hash: 0d5bb6140f45e23826bf2d0a3fc32cd19d9244dc47d127c28b66089fcfc3352a
- Author: supercent-io
- GitHub username: supercent-io
- License: MIT
- Repository: https://github.com/supercent-io/skills-template/tree/main/.agent-skills/task-estimation/
- Ref: 36e07d5e13068e5be64447e8f20b427cf2cbd21a
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/supercent-io-task-estimation
- Manifest: https://skillstore.pages.dev/api/skills/supercent-io-task-estimation/manifest

## Capabilities

- Maps task complexity to Fibonacci story point ranges.
- Explains a planning poker workflow for team consensus.
- Converts rough work into t-shirt size estimates.
- Adds buffers for risk and uncertainty.
- Provides an estimation document template with risks and dependencies.

## Use Cases

- Plan a sprint backlog: Estimate candidate stories, compare effort, and choose a realistic sprint scope.
- Shape a product roadmap: Turn feature ideas into rough sizes before sequencing quarterly work.
- Review engineering risk: Adjust estimates for unknowns, dependencies, integration work, and testing needs.

## Prompt Templates

### Estimate a single task

```
Estimate this task with story points, t-shirt size, time range, risks, dependencies, and assumptions: [task details].
```

### Prepare planning poker notes

```
Create planning poker notes for this story. Include questions, likely estimate range, risk factors, and reasons for high or low votes: [story].
```

### Split a large epic

```
Break this epic into smaller estimable stories. For each story, include acceptance criteria, estimate, dependencies, and open questions: [epic].
```

### Calibrate a roadmap estimate

```
Using this team velocity and backlog, estimate delivery ranges. Show confidence, sequencing risks, dependencies, and where estimates need discovery: [context].
```

## Limitations

- Requires clear task details, acceptance criteria, and dependencies.
- Does not inspect repositories or project history automatically.
- Estimates depend on each team's velocity and delivery context.
- Time ranges are planning aids, not delivery commitments.

## Best Practices

- Provide acceptance criteria before asking for an estimate.
- Compare each task with similar completed work.
- Separate high-risk unknowns into discovery tasks.

## Anti Patterns

- Do not treat estimates as promises from individuals.
- Do not estimate large epics without splitting them first.
- Do not ignore team velocity, dependencies, or technical risk.

## Security Audit

- Audited at: 2026-07-07T06:52:21.121\+00:00
- Summary: All external command findings are false positives from Markdown code fences and inline tags. The URL findings are reference links only, with no prompt injection or exfiltration intent found.

## Stats

- Views: 119
- Downloads: 16
- Favorites: 1
- Popularity score: 0