Agent skill · product strategy · aj-geddes
project-estimation
Estimate project scope, timeline, and resource requirements using multiple estimation techniques including bottom-up, top-down, and analogous estimation methods for accurate project planning.
Why this skill is useful
Provides domain-specific knowledge on project estimation techniques and includes a Python implementation for three-point estimation that the AI wouldn't reliably generate on its own.
What it needs
About 2k tokens when loaded. Last updated 2026-03-04. 307 stars on the source repository.
What this skill does
Project Estimation Table of Contents Overview When to Use Quick Start Reference Guides Best Practices Overview Accurate project estimation determines realistic timelines, budgets, and resource allocation. Effective estimation combines historical data, expert judgment, and structured techniques to minimize surprises. When to Use Defining project scope and deliverables Creating project budgets and timelines Allocating team resources Managing stakeholder expectations Assessing project feasibility Planning for contingencies Updating estimates during project execution Quick Start Minimal working example: Reference Guides Detailed implementations in the references/ directory: Guide Contents --- --- Three-Point Estimation (PERT) Three-Point Estimation (PERT) Bottom-Up Estimation Bottom-Up Estimation Analogous Estimation Analogous Estimation Resource Estimation Resource Estimation Estimation Templates Estimation Templates Best Practices ✅ DO Use multiple estimation techniques and compare results Include contingency buffers (15-25% for new projects) Base estimates on historical data from similar projects Break down large efforts into smaller components Get input from team members doing the actual work Document assumptions and exclusions clearly Review and adjust estimates regularly Track actual vs. estimated metrics for improvement Include non-development tasks (planning, testing, deployment) Account for learning curve on unfamiliar technologies ❌ DON'T Estimate without clear scope definition Use unrealistic best-case scenarios Ignore historical project data Estimate under pressure to hit arbitrary targets Forget to include non-coding activities Use estimates as performance metrics for individuals Change estimates mid-project without clear reason Estimate without team input Ignore risks and contingencies Use one technique exclusively
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aj-geddes/project-estimation