estimate

Generate confidence-weighted effort estimates from task complexity, dependencies, and risk.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill estimate-tranhieutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/estimate
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill estimate-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estimating task effort is painful without data, so this Skill translates vague requests into structured budgets by analyzing complexity, dependencies, historical velocity, and risk.

Core Features & Use Cases

  • Holistic Analysis: Reviews code impact, dependencies, and integration points to determine the true scope of change.
  • Historical Context: Scans past sprints and similar tasks to calibrate confidence levels and detect estimation bias.
  • Use Case: During sprint planning, provide a new feature description and receive optimistic, expected, and pessimistic day estimates with risk and dependency tables to justify the commitment.

Quick Start

Request an estimate by summarizing the task description so the Skill can analyze complexity, dependencies, and risks.

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I generate effort estimates for complex backlog tasks?

Generate effort estimates by providing a task description; the Skill analyzes code complexity, dependencies, and historical sprint data to report optimistic, expected, and pessimistic day budgets.

What is the best way to calculate risk-adjusted budgets for sprint planning?

Calculate risk-adjusted budgets by scanning past sprints and similar tasks to calibrate confidence levels and detect estimation bias, producing structured budgets with risk and dependency tables.

Can I use historical sprint velocity to calibrate task complexity analysis?

Yes, you can use historical sprint velocity to calibrate task complexity analysis. The Skill scans past sprints and similar tasks to detect estimation bias and adjust confidence levels accordingly.

How do I estimate infrastructure work when dependencies are unclear?

Estimate infrastructure work with unclear dependencies by analyzing integration points and risk factors. This translates vague requests into structured budgets with confidence levels and risk tables.

Why do my task estimates consistently miss expected effort targets?

Task estimates miss expected effort targets due to estimation bias. Scanning historical sprint data and similar tasks calibrates confidence levels to correct this drift and improve accuracy.

Does this approach work for both frontend and backend effort estimation?

Yes, this approach works for both frontend and backend effort estimation. It applies complexity analysis and dependency reviews to determine the true scope of change across infrastructure work.