task-estimation

Estimate software development tasks using story points, t-shirt sizing, and planning poker.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/supercent-io/skills-template --skill task-estimation-supercent-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-estimation
Source: https://github.com/supercent-io/skills-template/tree/main/.agent-skills/task-estimation
Command: npx skills add https://github.com/supercent-io/skills-template --skill task-estimation-supercent-io

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams accurately estimate the effort required for software development tasks, leading to better planning and more predictable delivery.

Core Features & Use Cases

  • Story Points: Utilizes the Fibonacci sequence for relative estimation.
  • Planning Poker: Facilitates team consensus through a structured voting process.
  • T-Shirt Sizing: Provides a quick, high-level estimation method.
  • Risk & Uncertainty Adjustment: Incorporates buffers for potential issues.
  • Use Case: During sprint planning, use this skill to estimate a new feature request using Planning Poker, ensuring the team agrees on the complexity and effort involved.

Quick Start

Estimate the story points for a new feature by following the Planning Poker process.

Frequently Asked Questions about task-estimation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate software development tasks using story points during sprint planning?

Estimate software development tasks using story points by applying the Fibonacci sequence for relative complexity assessment. This agile methodology enables your team to evaluate effort against reference tasks, producing consensus-driven sprint commitments.

What is planning poker and how does it work for agile estimation?

Planning poker is a structured voting process for agile estimation that facilitates team consensus. Team members independently estimate task complexity using story points, discuss discrepancies, and re-vote until agreement is reached, ensuring accurate effort prediction.

When should I use t-shirt sizing instead of story points for project management?

Use t-shirt sizing for quick, high-level estimation instead of story points when you need rapid relative complexity assessment early in project management. It provides a broad categorization of effort without the granularity required for detailed sprint planning.

How do I incorporate risk and uncertainty into agile task estimates?

Incorporate risk and uncertainty into agile task estimates by applying adjustment buffers for potential issues. This estimation approach accounts for unknown variables, generating a detailed estimation document that supports more predictable delivery.

Does agile estimation support relative complexity assessment for new feature requests?

Agile estimation supports relative complexity assessment for new feature requests by comparing them against existing work. Using methods like planning poker and story points, teams evaluate new features against a baseline to reach consensus on effort.