Estimates task effort into structured ranges with confidence and risk analysis.
npx skills add https://github.com/WindXRan/y3td --skill estimate-windxran
Please help me install this Agent Skill. Skill: estimate Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/estimate Command: npx skills add https://github.com/WindXRan/y3td --skill estimate-windxran
It helps teams turn vague tasks into actionable effort estimates by analyzing complexity, dependencies, historical velocity, and risk so planning stays realistic.
Use the estimate skill to create a structured days-range plan for the task you describe, including a recommended budget, confidence level, and the single biggest risk factor.
High-intent search queries and answers about installing and using this skill.
Software development effort estimation analyzes task descriptions to produce structured planning outputs with optimistic, expected, and pessimistic ranges. It evaluates code impact, integration points, test coverage needs, and historical sprint velocity to generate realistic effort estimates.
Yes, task estimation utilizes historical sprint velocity data from production sprint records to ground effort assumptions. By analyzing past velocity alongside current project context, it calculates expected effort ranges and confidence levels for new software changes.
Assessing code impact requires scanning relevant project modules and consulting design documents to identify affected files and integration points. This evidence-driven scope scanning determines test coverage needs and potential dependencies for accurate effort planning.
Yes, effort estimation reads project context directly from CLAUDE.md files and optionally consults design documents under design directories. This contextual awareness ensures that complexity analysis and risk factors align with the actual software architecture.
Including risk analysis in effort planning involves identifying the single biggest risk factor alongside dependency mapping and confidence levels. It transforms vague tasks into actionable estimates by evaluating complexity, integration points, and historical velocity data.
Structured effort estimates use rounded half-day increments to provide optimistic, expected, and pessimistic time ranges. This format includes a recommended budget, confidence level, and identified risk factors to keep sprint planning realistic.
easonlaoGenerate effort estimates with optimistic, expected, and pessimistic ranges.
XGanQAQEstimate engineering effort with optimistic, expected, and pessimistic ranges.
1024XEngineerReview code changes for correctness, regressions, and missing tests.
AlbertLin821Analyze git-staged changes to map upstream dependencies and affected execution flows.
