planning-estimation

Estimate project task time and effort using three-point, t-shirt sizing, or story points.

32|7|Updated Jan 28, 2026

Search Tags:#planning #estimation #assumptions #time #risk #effort

Ready to run

npx skills add https://github.com/OzeroHAX/AssistAgents --skill planning-estimation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning-estimation
Source: https://github.com/OzeroHAX/AssistAgents/tree/main/templates/skills/planning/estimation
Command: npx skills add https://github.com/OzeroHAX/AssistAgents --skill planning-estimation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured and transparent approach to estimating the time and effort required for tasks or projects, moving beyond simple guesswork.

Core Features & Use Cases

Method Selection: Choose from various estimation techniques like three-point, t-shirt sizing, or story points.
Range-Based Estimates: Provides estimates as a range (min/likely/max) to account for uncertainty.
Assumption Documentation: Clearly lists the assumptions made during the estimation process.
Risk Identification: Highlights factors that could impact the estimate, aiding in risk management.
Use Case: A development team needs to estimate the effort for a new feature. They use this Skill to break down the work, select a three-point estimation method, define assumptions about API availability, and list potential risks like unexpected technical debt.

Quick Start

Use the planning-estimation skill to provide a three-point estimate for the 'user authentication module' feature.

Frequently Asked Questions about planning-estimation

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

FAQPage Schema

How do I estimate project effort using ranges and assumptions?▼

To estimate project effort using ranges, you provide min, likely, and max time estimates for work items. This method details assumptions and influencing factors, ensuring transparent planning and managed expectations for development teams.

What is the best way to provide a three-point estimate for a software feature?▼

The best way to provide a three-point estimate is to break down the feature into tasks, define optimistic, likely, and pessimistic time ranges, and document assumptions like API availability alongside potential risks such as technical debt.

Can I use t-shirt sizing and story points for project time estimation?▼

Yes, you can use t-shirt sizing and story points for project time estimation. The method selection feature supports these techniques alongside three-point estimation to forecast project timelines and manage team expectations.

How do you document assumptions and risks during task estimation?▼

You document assumptions and risks during task estimation by explicitly listing the conditions assumed for the work and highlighting factors that could impact the time estimate. This facilitates transparent planning and proactive risk management.

Does range-based estimation work for managing uncertain project timelines?▼

Range-based estimation works for uncertain project timelines by providing minimum, likely, and maximum effort values. This approach accounts for uncertainty and supports project managers in forecasting schedules accurately.

What are the limitations of effort estimation without documented assumptions?▼

Effort estimation without documented assumptions relies on simple guesswork and lacks transparency. It fails to highlight influencing factors or risks, making it difficult to manage expectations or forecast project timelines accurately.