task-estimation

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estimate software development tasks accurately using story points, t-shirt sizing, planning poker, and risk-adjusted estimation. Use PROACTIVELY when planning sprints, estimating backlog items, sizing roadmap work, or any time task complexity and effort need to be quantified. Trigger on phrases like 'estimate this', 'how many points', 'story points', 'size this task', 'planning poker', 't-shirt sizing', 'how long will this take', 'sprint capacity', or any request involving effort estimation for software tasks.

Core Features & Use Cases

  • Relative estimation with Story Points (1, 2, 3, 5, 8, 13, 21)
  • Planning Poker collaboration to reach team consensus
  • T-Shirt sizing for quick backlog sizing
  • Risk and uncertainty adjustments to produce a final estimate
  • Use Case: Plan sprints, size backlog items, and forecast roadmap work with consistent estimates
  • Best practices: break down large items, reference past velocity, and re-estimate as understanding evolves

Quick Start

Provide a complete estimation for a user story, including story points, t-shirt size, and risk-adjusted time range.

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 and t-shirt sizing?

Estimate software development tasks by applying relative sizing with story points (1, 2, 3, 5, 8, 13, 21) or quick t-shirt sizing, then adjust for risk and uncertainty to produce a final effort estimate.

What is the best way to facilitate planning poker for sprint backlog sizing?

Planning poker facilitates team consensus for backlog sizing by having members collaboratively assign story points to tasks, ensuring accurate relative estimates for sprint planning and capacity forecasting.

How do I handle large backlog items that exceed 13 story points during estimation?

Large backlog items exceeding 13 story points should be split into smaller, actionable tasks. This best practice ensures accurate risk-adjusted estimation and prevents oversized work from disrupting sprint velocity.

When do I need risk-adjusted estimation for software task planning?

Risk-adjusted estimation is needed during sprint planning, backlog refinement, and roadmap sizing to quantify effort and anticipate timelines accurately by accounting for uncertainty and complexity in development tasks.

Can I use historical velocity references to improve roadmap estimation accuracy?

Historical velocity references improve roadmap estimation by providing baseline data to compare against new story point estimates, helping teams forecast capacity and size work consistently across sprints.

Does this approach support both quick backlog sizing and detailed sprint capacity planning?

This approach supports both quick t-shirt sizing for high-level backlog sizing and detailed story point estimation with risk adjustment for precise sprint capacity planning and roadmap forecasting.