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. This Skill produces a structured, evidence-based estimate by analyzing the actual code, dependencies, and past sprint data. ## Core Features & Use Cases - Complexity Analysis: Scans affected files and modules to assess code complexity, coupling, integration points, and test coverage needs. - Three-Scenario Estimates: Produces optimistic, expected, and pessimistic day estimates with a confidence level and explicit risk register. - Historical Grounding: Reads past sprint data from production/sprints/ and design docs from design/gdd/ to anchor estimates in real velocity. - Use Case: Before committing a new gameplay feature to a sprint, run the estimate to get a recommended budget in days, a breakdown into sub-tasks, and the single biggest risk factor to discuss with the team. ## Quick Start Use the estimate skill to estimate the effort for implementing the new inventory system and report the recommended budget and confidence level.
