skills.rest
claretagrapelike32
claretagrapelike32COMMUNITY
Explore all skills by this author →
GitHub

estimate

Generates structured task effort estimates with confidence levels and risk analysis.

Updated Aug 2, 2026
Search Tags:#project management#estimation#sprint planning#task sizing#velocity#risk analysis#three-point estimate
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill estimate-claretagrapelike32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/estimate
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill estimate-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Estimating software tasks is often guesswork that ignores codebase complexity, historical velocity, and hidden risks, leading to missed deadlines and poor sprint planning. ## Core Features & Use Cases - Complexity Analysis: Scans affected files and modules to assess code complexity, coupling, integration points, and test coverage needs. - Three-Point Estimates: Produces optimistic, expected, and pessimistic day estimates with an explicit confidence level and risk register. - Historical Grounding: Reads past sprint data from production/sprints/ and design docs from design/gdd/ to anchor estimates in actual team velocity. - Use Case: Before committing a new gameplay feature to a sprint, run this Skill to get a structured estimate with a suggested task breakdown, dependencies, and the single biggest risk factor. ## Quick Start Use the estimate skill to estimate the effort for implementing the new inventory system and report the recommended budget and confidence level.

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I estimate software task effort accurately?▼

Analyze the affected code for complexity and coupling, review historical velocity from past sprints, and produce a three-point estimate covering optimistic, expected, and pessimistic scenarios. This Skill automates that analysis and outputs a structured estimate report.

What is a three-point estimate in project planning?▼

A three-point estimate gives optimistic, expected, and pessimistic durations instead of a single number. The recommended budget is the expected value, and the spread between scenarios communicates uncertainty to the team.

Does this estimation skill modify project files?▼

No, the skill is read-only. It scans code, design documents, and sprint history to produce an estimate report, but writes nothing to the repository.

What should I do when an estimate has low confidence?▼

Run a time-boxed spike or prototype before committing to the task. Low confidence usually signals unfamiliar technology, ambiguous requirements, or unresolved dependencies that a spike can clarify.

When should a large task be broken down instead of estimated?▼

Tasks estimated over 10 days should be split into smaller stories before scheduling. Large estimates hide compounding uncertainty, and smaller stories give more reliable velocity data for future planning.

Related Skills

Explore More Product & Management Skills→
pixel-cellarpixel-cellar
277

estimate

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

Official
Advanced
hamzaPixlhamzaPixl
2

sprint-planning

Decompose epics into sprint tasks and generate a .context/sprint-plan.md output.

Community
Advanced
product-on-purposeproduct-on-purpose
527

develop-spike-summary

Document time-boxed spike results with findings and recommendations.

Official
Basic
getcrew44getcrew44
358

user-story-splitting

Split large user stories into independently deliverable stories using eight splitting patterns.

Official
Intermediate