Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Project Estimation

  • 562 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

project-estimation is a coding-agent skill that produces realistic timelines, budgets, and resource plans using structured estimation techniques for developers scoping software projects before implementation.

About

project-estimation is a skill from aj-geddes/useful-ai-prompts that guides accurate project scoping through bottom-up, top-down, and analogous estimation methods combined with historical data and expert judgment. It helps agents break work into estimable units, apply structured techniques to minimize surprise overruns, and document assumptions behind timeline and budget outputs. The skill includes quick-start guidance, reference guides, and best practices for when to re-estimate after scope changes. Developers reach for project-estimation when kicking off migrations, greenfield services, or multi-sprint features inside Cursor or Claude Code and need defensible hour, headcount, and milestone tables before writing production code. Output emphasizes realistic ranges and explicit dependencies rather than single-point guesses, making plans suitable for stakeholder review, sprint zero planning, or RFC appendices. Pair with architecture or TDD skills after scope is accepted to translate estimates into implementation phases.

  • Combines bottom-up, top-down, analogous, and three-point (PERT) estimation techniques
  • Generates contingency plans and risk-adjusted timelines
  • Produces stakeholder-ready scope, budget, and resource allocation artifacts
  • Supports estimate updates during project execution
  • Reduces timeline surprises through structured historical-data and expert-judgment methods

Project Estimation by the numbers

  • 562 all-time installs (skills.sh)
  • Ranked #709 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill project-estimation

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs562
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you estimate project scope and timelines?

Produce realistic timelines, budgets, and resource plans before committing to implementation.

Who is it for?

Tech leads and developers scoping new features or migrations who need structured estimation before committing to delivery dates.

Skip if: Developers mid-implementation who only need task-level time tracking without upfront scope or budget planning.

When should I use this skill?

A developer asks to estimate project scope, timeline, budget, or resource requirements before implementation starts.

What you get

Timeline and budget estimate document with technique breakdown, assumptions list, and resource allocation plan

  • Timeline estimate
  • Budget and resource plan
  • Assumptions document

By the numbers

  • Covers 3 estimation techniques: bottom-up, top-down, and analogous methods

Files

SKILL.mdMarkdownGitHub ↗

Project Estimation

Table of Contents

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:

# Three-point estimation technique for uncertainty

class ThreePointEstimation:
    @staticmethod
    def calculate_pert_estimate(optimistic, most_likely, pessimistic):
        """
        PERT formula: (O + 4M + P) / 6
        Weighted toward most likely estimate
        """
        pert = (optimistic + 4 * most_likely + pessimistic) / 6
        return round(pert, 2)

    @staticmethod
    def calculate_standard_deviation(optimistic, pessimistic):
        """Standard deviation for risk analysis"""
        sigma = (pessimistic - optimistic) / 6
        return round(sigma, 2)

    @staticmethod
    def calculate_confidence_interval(pert_estimate, std_dev, confidence=0.95):
        """
        Calculate confidence interval for estimate
        95% confidence ≈ ±2 sigma
        """
        z_score = 1.96 if confidence == 0.95 else 2.576
// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Three-Point Estimation (PERT)Three-Point Estimation (PERT)
Bottom-Up EstimationBottom-Up Estimation
Analogous EstimationAnalogous Estimation
Resource EstimationResource Estimation
Estimation TemplatesEstimation 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

Related skills

How it compares

Pick project-estimation for upfront scope and timeline planning; use task-breakdown skills when work is already scoped and only needs granular tickets.

FAQ

Which estimation methods does project-estimation use?

project-estimation applies bottom-up, top-down, and analogous estimation techniques to scope timelines, budgets, and resource needs. Agents break work into estimable units, compare against historical data where available, and document assumptions so stakeholders see how ranges we

When should developers invoke project-estimation?

project-estimation fits greenfield features, migrations, or multi-sprint initiatives before coding starts. Developers invoke it when stakeholders need defensible hour, headcount, and milestone tables, or when scope changes require a structured re-estimation pass with updated assu

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.