estimation-stinger

Diagnoses estimation dysfunctions and applies probabilistic forecasting methods to software delivery predictions.

72|28|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/that-git-life --skill estimation-stinger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimation-stinger
Source: https://github.com/legioncodeinc/that-git-life/tree/main/.claude/skills/estimation-stinger
Command: npx skills add https://github.com/legioncodeinc/that-git-life --skill estimation-stinger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams replace unreliable software estimates with disciplined sizing practices, evidence-based forecasting, and clearer communication about delivery uncertainty.

Core Features & Use Cases

  • Estimation Framework Guidance: Applies Fibonacci story points, T-shirt sizing, Planning Poker, and relative sizing practices while preventing misuse of estimates as commitments.
  • Probabilistic Forecasting: Guides teams through throughput-based forecasting, Monte Carlo simulations, confidence percentiles, and NoEstimates approaches for realistic delivery predictions.
  • Estimation Dysfunction Diagnosis: Identifies planning fallacy, estimation drift, stakeholder commitment traps, and granularity problems to recommend the appropriate technique.
  • Use Case: Help an engineering team explain why sprint estimates keep missing deadlines, choose a better forecasting approach, and communicate P50/P85/P95 delivery confidence to stakeholders.

Quick Start

Use the estimation-stinger skill to analyze why our software estimates are inaccurate and recommend an evidence-based forecasting approach.

Frequently Asked Questions about estimation-stinger

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

FAQPage Schema
Why do our agile sprint estimates keep missing deadlines and how can we forecast better?

Sprint estimates miss deadlines due to planning fallacy, estimation drift, and stakeholder commitment traps. Diagnose these estimation dysfunctions and apply probabilistic forecasting with Monte Carlo simulations to predict realistic delivery confidence percentiles.

What is the best way to transition from story points to NoEstimates for software delivery?

Transitioning to NoEstimates involves evaluating throughput-based forecasting methods instead of relative sizing. This approach replaces traditional story point calibration with evidence-based probabilistic prediction to generate realistic delivery timelines.

How do I calculate P50, P85, and P95 delivery confidence for stakeholders?

Calculate P50, P85, and P95 delivery confidence by running Monte Carlo simulations on historical throughput data. This probabilistic forecasting method generates delivery percentiles that communicate schedule uncertainty clearly to stakeholders.

How do you calibrate story points using Planning Poker to prevent estimation misuse?

Calibrate story points using Planning Poker and Fibonacci sequences to establish relative sizing discipline. This prevents estimation misuse as commitments by focusing on comparative effort rather than absolute time guarantees.

When should I use Monte Carlo simulations vs T-shirt sizing for agile planning?

Use Monte Carlo simulations for probabilistic delivery forecasting across multiple sprints, and T-shirt sizing for quick relative sizing of individual backlog items. Choose based on whether you need schedule prediction or task granularity assessment.

Can estimation-stinger diagnose planning fallacy issues in our software development process?

Yes, estimation-stinger diagnoses planning fallacy, estimation drift, and granularity problems within your development process. It then recommends the appropriate evidence-based forecasting technique to improve delivery prediction accuracy.