estimate

Effort estimation for software tasks requires scanning impacted code areas, analyzing integration points, and reviewing sprint history to generate optimistic, expected, and pessimistic ranges. This skill reads project context from CLAUDE.md and design docs to produce range-based estimates with confidence levels and the biggest risk factor.

Calculating sprint velocity for project planning involves analyzing prior sprint data from your sprint history directory and combining it with dependency analysis and test coverage assessment. This skill reviews historical velocity data alongside complexity factors to output structured effort estimates with clear risk identification.

Yes, risk analysis for code changes involves scanning affected code areas, identifying integration points, and assessing test coverage needs before delivery commitments. This skill outputs a range-based estimate with a confidence level and highlights the single biggest risk factor for your software change planning.

Dependency analysis for effort planning works by scanning impacted code areas, identifying integration points, and reviewing test coverage requirements alongside historical sprint velocity. This skill combines these factors with project context from CLAUDE.md to generate structured estimates with confidence and risk assessment.

Yes, a detailed task description is needed for accurate effort estimation. This skill checks whether your task description is detailed enough to estimate and requests clarification if the scope is ambiguous, ensuring the analysis of complexity, dependencies, and risk factors produces reliable results.

Test coverage assessment for effort estimation needs project context from CLAUDE.md and relevant design documents under design directories. This skill reads these files alongside sprint history data to evaluate affected code areas and integration points before generating range-based effort estimates.