estimate

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

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill estimate-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/estimate
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill estimate-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you turn an uncertain task into a realistic effort estimate by breaking down scope, dependencies, risk, and test needs before work begins.

Core Features & Use Cases

  • Effort Analysis: Evaluates task complexity, integration points, and validation needs to produce a practical estimate.
  • Risk-Aware Planning: Accounts for contract changes, migrations, operational impact, and uncertainty so the estimate reflects real project risk.
  • Use Case: A product team can ask for an estimate on a new API change and get a structured breakdown with optimistic, expected, and pessimistic effort ranges.

Quick Start

Ask the estimate skill to assess the task you want planned, such as estimating a new feature, bug fix, or platform change.

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I estimate effort for a software feature with unclear scope and dependencies?

To estimate effort for a software feature, you need to analyze task scope, integration points, and delivery risk. Providing clear task details and project context generates a structured breakdown with optimistic, expected, and pessimistic effort ranges.

What is the best way to plan effort analysis for a platform migration?

Effort analysis for a platform migration requires evaluating complexity, dependencies, and operational impact. This risk-aware planning approach accounts for uncertainty and validation needs to produce a realistic estimate reflecting actual project risk.

Can I get a risk assessment for a contract change before starting development?

Yes, you can get a risk assessment for a contract change by analyzing the task scope and dependencies. The assessment evaluates operational impact and uncertainty, returning confidence levels and mitigation notes alongside expected effort ranges.

Does project scoping for an API change include test and validation needs?

Project scoping for an API change includes evaluating validation needs and integration points. Analyzing these test requirements alongside complexity ensures the structured effort estimate accurately reflects the total delivery risk.

What do I need to provide for accurate product planning and task estimates?

For accurate product planning and task estimates, you must provide clear task details and relevant project context. This input allows the analysis of complexity, scope, and dependencies required to generate realistic effort ranges.

Why does my task estimate include optimistic, expected, and pessimistic ranges?

Your task estimate includes optimistic, expected, and pessimistic ranges to account for uncertainty and delivery risk. This structured breakdown ensures risk-aware planning by reflecting varying complexity levels and potential mitigation needs.