Verified:GitHub

estimate

Name: estimate
Availability: InStock
Author: kay6198835

Analyze task complexity, dependencies, velocity history, and risk factors to generate structured effort estimates with confidence levels.

Updated Feb 8, 2024

Search Tags:#planning #complexity #velocity #risk #task #estimate

Ready to run

npx skills add https://github.com/kay6198835/Game-RPG --skill estimate-kay6198835

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: estimate
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/estimate
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill estimate-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Estimates task effort by analyzing complexity, dependencies, historical velocity, and risk factors. Produces a structured estimate with confidence levels.

Core Features & Use Cases

Analyze task attributes (complexity, dependencies, and velocity history) to forecast effort.
Generate a structured estimate with confidence levels and recommended ranges for planning.
Use in sprint planning, resource allocation, and milestone forecasting.

Quick Start

Provide a task description when prompted and allow the system to generate an estimate following its Phase 1–4 workflow.

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 using complexity and velocity history?▼

Estimate task effort by analyzing complexity, dependencies, velocity history, and risk factors to produce a structured forecast with confidence levels. The system evaluates affected files and integration points to generate recommended planning ranges.

Can I use historical sprint data to forecast effort for cross-team initiatives?▼

Historical sprint data is required to forecast effort for cross-team initiatives. The system uses velocity history alongside task attributes like complexity and dependencies to generate structured estimates with confidence levels for resource allocation.

What is the best way to plan sprint effort when dealing with integration points and risk factors?▼

The best way to plan sprint effort is providing a task description to trigger a structured estimation workflow. It analyzes integration points, validation needs, and risk factors to produce a traceable forecast with confidence levels and recommended ranges.

Does effort estimation work for data work and software tasks without external dependencies?▼

Effort estimation works for data work and software tasks without external dependencies. It supports deterministic steps and ensures traceable assumptions by analyzing task complexity, velocity history, and validation needs to produce structured forecasts.

How does risk factor analysis improve project planning and milestone forecasting?▼

Risk factor analysis improves project planning by incorporating affected files, integration points, and historical sprint data into effort estimation. This generates structured forecasts with confidence levels, enabling reliable milestone forecasting and resource allocation.

Why do I need to consider affected files and validation needs when estimating task complexity?▼

Considering affected files and validation needs is required because the system uses them to analyze task complexity and dependencies. This ensures traceable assumptions and produces structured estimates with confidence levels for accurate sprint planning.