Generate effort estimates with optimistic, expected, and pessimistic ranges.
npx skills add https://github.com/easonlao/jiazi-game --skill estimate-easonlao
Please help me install this Agent Skill. Skill: estimate Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/estimate Command: npx skills add https://github.com/easonlao/jiazi-game --skill estimate-easonlao
This Skill helps you turn an unclear or complex task into a structured, decision-ready effort estimate with confidence and explicit risk.
Ask the estimate skill to estimate the effort for the task: "Implement a save/load system for the Jiazi Chronicle game, including basic state serialization and UI entry points."
High-intent search queries and answers about installing and using this skill.
Generate effort estimates for software tasks by analyzing complexity, dependencies, historical sprint velocity, and risk factors to produce optimistic, expected, and pessimistic ranges with a recommended budget and confidence level.
Map dependencies and risks for project planning by scanning project context and sprint history to highlight key risk factors, mitigations, and potential blocking dependencies alongside the structured effort estimate.
Calculate sprint velocity for engineering workflow estimates by reviewing sprint history under production/sprints/ to inform scope and uncertainty, applying historical velocity data to structured effort ranges.
Use project context and design documents to inform task effort estimation by loading context from CLAUDE.md and scanning relevant design documents under design/gdd/ to identify affected code paths and integration points.
Effort estimation works for complex tasks with unclear scope by turning them into structured, decision-ready estimates with explicit risk, sub-task breakdowns, and confidence levels based on available project context.
Automated effort estimation for development planning relies on available project context, design documents, and sprint history; estimates are limited by the completeness of this input data and the accuracy of historical velocity records.
rakhnianskii9Generate changelogs from git commits, sprint data, and design documents.
scomofoEstimate engineering task effort from scope, dependencies, and sprint evidence.
AlbertLin821Analyze git-staged changes to map upstream dependencies and affected execution flows.
wsmanAnalyze task scope, dependencies, complexity, and delivery risk to produce effort estimates.
