skills.rest
onemanking
onemankingCOMMUNITY
Explore all skills by this author →
GitHub

estimate

Generates structured task effort estimates with confidence levels and risk analysis.

Updated Apr 13, 2026
Search Tags:#project planning#task breakdown#estimation#sprint planning#velocity#risk analysis#effort estimate
One-click install
npx skills add https://github.com/onemanking/the-operator --skill estimate-onemanking
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/estimate
Command: npx skills add https://github.com/onemanking/the-operator --skill estimate-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Estimating software tasks is error-prone: single-point guesses create false precision, hidden risks surface mid-sprint, and scope ambiguity derails planning. This Skill produces structured, range-based estimates grounded in codebase analysis and historical sprint data. ## Core Features & Use Cases - Complexity and Scope Analysis: Scans affected files, dependencies, integration points, and test coverage to size the work objectively. - Three-Point Estimates: Produces optimistic, expected, and pessimistic day ranges with an explicit confidence level and risk register. - Historical Calibration: Compares against past sprint data to detect estimation bias and apply correction factors. - Use Case: Before sprint planning, ask for an estimate on "add utility minigame module" and receive a breakdown of sub-tasks, dependencies, key files, and the biggest risk factor. ## Quick Start Ask the assistant to estimate the effort for a specific task description, for example: estimate how long it would take to add a new tool button to the control grid.

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I estimate software task effort accurately?▼

Provide a clear task description and the skill analyzes affected files, dependencies, integration points, and test coverage to produce a three-point estimate. It also checks historical sprint data for similar tasks to calibrate the estimate against actual past performance.

How to estimate tasks with unclear requirements?▼

When requirements are vague, the skill asks for clarification before estimating. If confidence remains low after analysis, it recommends a time-boxed spike or prototype rather than committing to a full estimate.

What is a three-point estimate in project planning?▼

A three-point estimate gives optimistic, expected, and pessimistic scenarios instead of a single number. The recommended budget uses the expected value, and the spread between scenarios communicates uncertainty to stakeholders.

When should a task be broken down instead of estimated?▼

Tasks expected to exceed 10 days should be split into smaller sub-tasks and estimated individually. Large single estimates carry too much uncertainty, and the skill explicitly recommends decomposition in these cases.

Why do software estimates consistently run over budget?▼

Estimates fail due to scope ambiguity, hidden dependencies, and optimism bias. The skill counters this by listing explicit assumptions, risk factors with likelihood and impact, and correction factors derived from historical planned-versus-actual data.

Related Skills

Explore More Product & Management Skills→
devsforgedevsforge
39

project-planning

Convert software ideas into structured project plans with user stories and acceptance criteria.

Official
Basic
gcamptongcampton

gteam-project-manager

Convert ambiguous project requirements into executable plans with scoped tasks, owners, and acceptance criteria.

Community
Advanced
mbwsimsmbwsims
71

hotspots

Identify high-risk files in a codebase using churn, complexity, and coupling.

Community
Intermediate
dipandhali2021dipandhali2021

task-estimation

Estimate software tasks with story points, t-shirt sizing, and planning poker.

Community
Advanced