skills.rest
XGanQAQ
XGanQAQCOMMUNITY
Explore all skills by this author →
GitHub

estimate

Estimate engineering effort with optimistic, expected, and pessimistic ranges.

1|Updated May 5, 2026
Search Tags:#sprint planning#test coverage#risk assessment#effort estimation#software planning#code impact analysis#historical velocity
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill estimate-xganqaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/estimate
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill estimate-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The estimate skill turns a vague or complex task request into a structured effort plan by analyzing scope, impacted code, dependencies, and risk so teams can budget and schedule more reliably.

Core Features & Use Cases

  • Task clarification: Detects when the input is too vague to estimate meaningfully and requests clarification.
  • Project-aware estimation: Reads CLAUDE.md for context, then targets relevant design documents under design/gdd/ for feature-related tasks.
  • Impact-driven scanning: Identifies affected files and modules, checks for integration points, reviews existing test coverage, and uses production/sprints/ for historical velocity.
  • Actionable output: Produces optimistic/expected/pessimistic ranges, confidence level, dependencies, and a sub-task breakdown with half-day rounding.
  • Operational next steps: Advises spikes for low-confidence work, breaks large tasks into stories when needed, and recommends sprint planning updates.

Quick Start

Use the estimate skill to produce a task plan by running: estimate the effort for implementing the enemy AI behavior and pathfinding rework, including tests and integration with the current navigation system.

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I estimate engineering effort for a complex software task?▼

To estimate engineering effort, analyze task clarity, project context, affected code, and historical sprint velocity to produce a structured plan with optimistic, expected, and pessimistic ranges.

What's the best way to assess code impact and test coverage for sprint planning?▼

Assess code impact and test coverage by identifying affected files and modules, checking integration points, and reviewing existing tests alongside historical velocity data to inform your sprint planning.

How do I create a sub-task breakdown with effort estimation ranges?▼

Create a sub-task breakdown by scanning impacted modules and integration points, then generate a structured estimate with half-day rounding and optimistic, expected, and pessimistic effort ranges.

Can I use historical sprint velocity to calculate a recommended budget for software changes?▼

Yes, you can use historical sprint velocity from production sprints to calculate a recommended budget, producing a confidence level, dependencies, and risk assessment for your software changes.

When should I request task clarification before starting effort estimation?▼

You should request task clarification before effort estimation when the input is too vague to estimate meaningfully, ensuring the final effort plan accounts for all design-document dependencies.

Why does risk assessment matter for software planning and effort estimation?▼

Risk assessment matters for software planning because it identifies integration points and code impact, allowing you to advise spikes for low-confidence work and break large tasks into stories.

Related Skills

Explore More Software Engineering Skills→
easonlaoeasonlao

estimate

Generate effort estimates with optimistic, expected, and pessimistic ranges.

Community
Intermediate
ag-gridag-grid
477

estimate-jira

Generate structured JIRA ticket estimates with complexity, effort, and risk analysis.

Official
Advanced
imgamerimgamer

estimate

Generate range-based effort estimates from code, dependencies, and sprint history.

Community
Intermediate
CarlosQ96CarlosQ96

estimate

Estimate software task effort with optimistic, expected, and pessimistic day ranges.

Community
Intermediate