estimate

Estimate engineering task effort from scope, dependencies, and sprint evidence.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill estimate-scomofo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/estimate
Command: npx skills add https://github.com/scomofo/dragon-forge --skill estimate-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces uncertainty in planning by turning a vague task into a structured effort estimate grounded in complexity, dependencies, historical velocity, and risk.

Core Features & Use Cases

  • Task scoping: Clarifies what’s being asked and flags when requirements are too vague to estimate.
  • Impact scanning: Identifies affected modules/files, checks integration points, and finds existing test coverage relevant to the change.
  • Evidence-informed estimation: Incorporates similar past work from sprint evidence and evaluates risk factors to select an optimistic/expected/pessimistic range.
  • Actionable output: Produces a table-driven estimate with confidence level, risk register, dependencies, and a suggested sub-task breakdown.

Quick Start

Ask the AI to estimate a specific engineering task by providing a clear task description as the input argument.

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 sprint planning with dependencies and risk factors?

To estimate engineering effort for sprint planning, you provide a clear task description so the system can analyze scope, impacted modules, and integration points, outputting optimistic/expected/pessimistic ranges with a recommended budget.

What is confidence-based effort estimation in software project scoping?

Confidence-based effort estimation is a planning technique that evaluates task complexity, integration points, and historical sprint velocity to produce structured delivery timelines with attached confidence levels and risk registers.

How do I map dependencies and risk analysis for a new engineering task?

You map dependencies and risk analysis by scanning relevant design docs and production sprint evidence to identify affected code modules, check test coverage, and flag delivery risks before finalizing your project scoping.

Can I use historical sprint velocity to calculate optimistic and pessimistic task estimates?

Yes, you can use historical sprint velocity to calculate task estimates by incorporating similar past work and production evidence to generate accurate optimistic, expected, and pessimistic delivery ranges.

Do I need an AGENTS.md file to generate a task effort estimate?

Yes, you need an AGENTS.md file to generate a task effort estimate because the system requires reading project context from it to properly analyze task scope and impacted code modules.

What's the best way to break down vague engineering tasks into sub-tasks for estimation?

The best way to break down vague engineering tasks is to use impact scanning to identify affected files and integration points, producing an actionable table-driven estimate with a suggested sub-task breakdown.