project-estimation

Estimates agent-led project delivery time, token cost, and quota capacity from validated scope.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill project-estimation-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-estimation
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/project-estimation
Command: npx skills add https://github.com/sumitake/agent-collab --skill project-estimation-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Estimating how long an agent-led project will take and what it will cost is usually guesswork based on person-hours or invented labor rates. This Skill produces empirical delivery estimates from a validated scope, keeping wall-clock time, calendar elapsed time, API-equivalent token cost, marginal cash, and quota capacity as separate, honest figures. ## Core Features & Use Cases - Four modes: Estimate (forecast a scoped project), Reconcile (compare a prior estimate with verified actuals), Calibrate (rebuild empirical cohorts and priors), and Audit (check data integrity, freshness, and pricing provenance). - Deterministic offline helper: Runs a packaged Python helper with validated JSON inputs for request, prior, pricing, and quota data, never making provider calls or scraping prices. - Delivery-estimate checkpoint: Embeds a compact estimate section into formal implementation designs or plans, with typed results like estimate_unavailable instead of fabricated numbers. - Use Case: Before finalizing an implementation plan, invoke the skill to get P50/P80/P95 ranges for agent wall-clock time, calendar elapsed time, and API-equivalent token cost, with confidence and evidence coverage stated. ## Quick Start Ask the agent to estimate this project's wall-clock time and API-equivalent token cost based on the scoped phases and routes in the implementation plan.

Frequently Asked Questions about project-estimation

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

FAQPage Schema
How do I estimate how long an agent-led project will take?▼

Construct a structured request with phases, dependency edges, routes, and a completion boundary, then run the packaged offline helper with prior, pricing, and quota JSON inputs. It returns P50/P80/P95 ranges for wall-clock time, calendar elapsed time, and token cost.

How do I reconcile a project estimate with actual results?▼

Use the reconcile mode with verified actual evidence after the project completes. It compares the prior estimate against observed outcomes so you can see why an estimate missed and improve future calibration.

Does the estimation helper call provider APIs or scrape pricing?▼

No. The helper runs fully offline with explicit validated JSON inputs and never makes provider calls, scrapes prices, or infers labor rates. Pricing data comes from a packaged snapshot classified as official, estimated, or unpriced.

What happens when there is not enough scope to estimate a project?▼

The skill records a typed estimate_unavailable result with a reason such as insufficient_scope or unavailable_no_token_prior. It never converts missing evidence into zero cost or fabricates numbers to fill the gap.

When should the delivery-estimate checkpoint run during planning?▼

Invoke it after scope, phases, dependency edges, agent roles, and external gates are concrete but before final presentation of a design or plan. It runs at most once per distinct artifact-scope hash and embeds a compact headline section.