task-estimation

Convert feature descriptions into relative effort metrics using Fibonacci-based scoring.

Updated Dec 20, 2023
One-click install
npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill task-estimation-thiago-cruz-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-estimation
Source: https://github.com/Thiago-Cruz-eng/Hibrygame/tree/main/.claude/skills/task-estimation
Command: npx skills add https://github.com/Thiago-Cruz-eng/Hibrygame --skill task-estimation-thiago-cruz-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid vague or inconsistent planning by translating work into relative estimates (story points, T-shirt sizing) and agreeing on them using shared techniques.

Core Features & Use Cases

  • Story Points (relative complexity): Uses a Fibonacci-based scale to standardize how tasks are sized, with guidance on what each point range means.
  • Planning Poker: Facilitates team consensus through simultaneous card selection, discussion of outliers, and re-voting.
  • T-Shirt Sizing: Provides a fast mapping from rough effort categories (XS to XL) to story-point ranges for backlog grooming and early planning.
  • Risk & uncertainty adjustment: Recommends adding buffers based on risk level and quantified uncertainty to produce a more realistic estimate.
  • Output-ready template: Produces a structured estimation document including description, acceptance criteria, breakdown, risks, dependencies, and notes.

Example use case: estimating stories for a sprint by breaking down a feature into frontend, backend, and testing parts, then reconciling differences via planning poker.

Quick Start

Use the task-estimation skill to estimate a new user story for sprint planning by assigning story points using the Fibonacci scale and confirming team agreement via planning poker.

Frequently Asked Questions about task-estimation

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

FAQPage Schema
How do I estimate story points for sprint planning using planning poker?

To estimate story points for sprint planning, facilitate team consensus through simultaneous planning poker card selection, discuss outliers, and re-vote to assign Fibonacci-based scores.

What's the best way to convert T-shirt sizing to story points for backlog grooming?

The best way to convert T-shirt sizing to story points for backlog grooming is to map rough effort categories from XS to XL directly into defined Fibonacci-based point ranges.

How does risk buffering work when estimating agile tasks?

Risk buffering in agile task estimation works by recommending specific buffers based on quantified uncertainty and defined risk levels, producing more realistic roadmap forecasts.

Can I estimate integration tasks and CRUD work using relative effort metrics?

Yes, you can estimate integration tasks and CRUD work by converting feature descriptions into consistent relative effort metrics, applying Fibonacci-based scoring across common scenarios.

What is included in a structured task estimation output document?

A structured task estimation output document includes the task description, acceptance criteria, breakdown, risks, dependencies, and notes to guide sprint planning and roadmap forecasting.

Why should I use relative complexity sizing instead of hours for feature development?

Using relative complexity sizing instead of hours for feature development standardizes how tasks are sized across the team, avoiding vague planning by translating work into consistent story points.