estimate

Analyze task complexity, dependencies, and velocity to generate structured estimates with confidence levels.

277|65|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill estimate-pixel-cellar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/pixel-cellar/Claude-Code-Game-Studios/tree/main/.claude/skills/estimate
Command: npx skills add https://github.com/pixel-cellar/Claude-Code-Game-Studios --skill estimate-pixel-cellar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly estimate the effort required for a task by analyzing multiple inputs and producing a structured estimate with confidence levels.

Core Features & Use Cases

  • Read the task description and existing context to scope work accurately.
  • Analyze codebase impact, dependencies, historical sprint velocity, and risk factors to generate an evidence-based estimate.
  • Produce a structured estimate including optimistic/expected/pessimistic scenarios and a recommended contingency.

Quick Start

Provide a task description, and I will return a structured estimate with confidence levels.

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I estimate task effort for software development with confidence levels?

Task effort estimation analyzes complexity, dependencies, velocity history, and risk to produce a structured estimate with confidence levels. It scans the codebase for impacted modules and generates optimistic, expected, and pessimistic scenarios with a recommended contingency.

What inputs do I need to generate a sprint forecast for a development task?

Sprint forecasting requires a task description and project context from CLAUDE.md. It reviews relevant design docs and scans the codebase for impacted modules to generate an evidence-based estimate across design, implementation, and testing phases.

Can I use codebase analysis to predict task workload for impacted modules?

Yes, codebase analysis predicts task workload by scanning impacted modules and reading existing project context. It combines this with dependency mapping and historical sprint velocity to generate a structured estimate with confidence levels.

Does project planning estimate risk and contingency for development tasks?

Project planning estimates risk and contingency by analyzing task complexity and velocity history. It produces structured scenarios including optimistic, expected, and pessimistic outcomes alongside a recommended contingency buffer.

What is the best way to scope work accurately for a new development task?

Scoping work accurately involves reading the task description, ingesting project context, reviewing design docs, and scanning the codebase. This multi-input analysis produces an evidence-based estimate with structured confidence levels.

Why does task estimation include optimistic, expected, and pessimistic scenarios?

Task estimation includes optimistic, expected, and pessimistic scenarios to account for complexity and risk factors. This structured approach provides confidence levels and a recommended contingency to improve sprint forecasting accuracy.