skills.rest
FrancisVarga
FrancisVargaCOMMUNITY
Explore all skills by this author →
GitHub

estimate

Estimate software task effort from complexity, dependencies, and risk factors.

Updated May 13, 2026
Search Tags:#sprint planning#risk assessment#dependency mapping#effort sizing#estimate#software QA
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill estimate-francisvarga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/estimate
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill estimate-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of unclear or biased task sizing by producing a structured estimate that accounts for complexity, dependencies, and risk.

Core Features & Use Cases

  • Task understanding & clarification: Detects vague requests and prompts for clarification when estimating would be unreliable.
  • Impact-aware code scanning: Identifies likely files, modules, integration points, and existing test coverage in the affected areas.
  • Complexity, scope, and risk decomposition: Breaks down code complexity, scope changes, and uncertainty drivers to set confidence and contingencies.
  • Decision-ready output: Returns optimistic/expected/pessimistic ranges, a recommended budget, confidence level, risk factors, and dependency status.

Quick Start

Ask: "Estimate the effort for implementing a new matchmaking feature with database persistence, including tests and QA plan."

Frequently Asked Questions about estimate

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

FAQPage Schema
How do I get reliable effort estimates for software development tasks?▼

Effort estimates are produced by analyzing complexity, dependencies, historical velocity, and risk factors. The output provides a days-based range with a recommended budget before execution, ensuring structured and confidence-driven task sizing.

How does risk assessment and dependency mapping improve sprint planning?▼

Risk assessment and dependency mapping improve sprint planning by scanning impacted files and sprint history to identify uncertainty drivers. This decomposition sets confidence levels and explicit contingencies for a decision-ready output.

What should I do if my task description is too vague for effort sizing?▼

Effort sizing detects vague requests and prompts for clarification when estimating would be unreliable. This ensures the system has sufficient context before attempting to calculate a days-based range and recommended budget.

Can I estimate effort for tasks that require database persistence and QA planning?▼

Estimating effort for tasks with database persistence and QA planning is fully supported. The process scans impacted files, modules, and existing test coverage to break down code complexity and output optimistic, expected, and pessimistic ranges.

What is the best way to structure task sizing for impacted code and tests?▼

The best way to structure task sizing is by reading task context from CLAUDE.md, checking design documents in design/gdd/, and scanning impacted files in production/sprints/. This yields confidence-driven effort with explicit risk and dependencies.

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

Effort estimates include optimistic, expected, and pessimistic ranges to account for complexity, scope changes, and uncertainty drivers. This decision-ready output provides a recommended budget and confidence level before execution begins.

Related Skills

Explore More Product & Management Skills→
easonlaoeasonlao

estimate

Generate effort estimates with optimistic, expected, and pessimistic ranges.

Community
Intermediate
fengqiliufengqiliu
2

pm-alpha-task-prioritization

Prioritize tasks with RICE scoring and Eisenhower matrix for sprint planning.

Community
Intermediate
imgamerimgamer

estimate

Generate range-based effort estimates from code, dependencies, and sprint history.

Community
Intermediate
SeongHuniSeongHuni

estimate

Analyze code complexity, dependencies, and risk factors to generate effort estimates.

Community
Advanced