estimate

Analyze task complexity, dependencies, and risk to produce structured effort estimates.

Updated Apr 8, 2026

Search Tags:#planning #dependencies #complexity #velocity #risk #estimate

Ready to run

npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill estimate-hechaoyannet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/estimate
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill estimate-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.

Core Features & Use Cases

Phase-driven estimation: Guides planning by calculating effort, risk, and required capacity.
Structured breakdown: Produces a task description, complexity factors, and a recommended breakdown.
Use Case: Plan sprints by generating estimates for features, bugs, and research tasks with a clear confidence level.

Quick Start

Describe the task to receive a complete estimate with recommended breakdown and risk factors.

Frequently Asked Questions about estimate

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

FAQPage Schema

How do I estimate software development effort for features and bugs?▼

To estimate software development effort, you analyze task complexity, dependencies, historical velocity, and risk factors. This process generates a structured breakdown with effort scenarios and confidence levels to guide sprint planning.

What is phase-by-phase analysis in task effort estimation?▼

Phase-by-phase analysis in task effort estimation evaluates complexity, dependencies, and risk for each project stage. It calculates required capacity and produces a formal breakdown including effort scenarios and recommended task decomposition.

How do I plan sprints using historical velocity and complexity factors?▼

Plan sprints by applying historical velocity and complexity factors to your task descriptions. This yields a structured estimate with confidence levels, covering features, bugs, and research work within your project planning workflow.

Can I generate a structured estimate with confidence levels for research tasks?▼

Yes, you can generate a structured estimate with confidence levels for research tasks. The estimation process analyzes dependencies and risk factors to produce a formal breakdown, effort scenarios, and recommended task decomposition.

Does task effort estimation work for project planning workflows with high risk factors?▼

Task effort estimation works for project planning workflows with high risk factors by explicitly analyzing those risks alongside dependencies and complexity. It outputs a structured estimate with confidence levels and a recommended breakdown to manage uncertainty.

Why do I need a recommended breakdown when calculating task effort?▼

You need a recommended breakdown when calculating task effort to decompose complex tasks into manageable phases. This structured breakdown aligns effort scenarios, dependencies, and risk factors with your historical velocity for accurate capacity planning.