eta

Estimate coding task duration by analyzing codebase scope and task description.

60|2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill eta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eta
Source: https://github.com/ElliotJLT/Claude-Skill-Potions/tree/main/skills/eta
Command: npx skills add https://github.com/ElliotJLT/Claude-Skill-Potions --skill eta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides data-driven time estimates for coding tasks by analyzing the codebase scope and the task description, reducing the planning guesswork.

Core Features & Use Cases

  • Codebase scope analysis to measure files, lines, tests, and complexity markers.
  • Generation of low-to-high time estimates with breakdown by phase (analysis, implementation, testing, verification) and checkpoint recommendations.
  • Clear risk factors and checkpoints to guide planning and incremental delivery.
  • Example: Before starting a feature, run the ETA to obtain a realistic time window and plan sprints.

Quick Start

Run the estimation for a given task using the helper script against the target codebase.

  • Run: python scripts/estimate_task.py --task "<task description>" --path "<codebase_path>"
  • Optional flags: --files <n> to override scope, --json for structured output

Frequently Asked Questions about eta

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

FAQPage Schema
How do I estimate task duration before starting a coding project?

Task estimation analyzes your codebase scope—files, lines, tests, complexity markers—against your task description to generate low-to-high time windows with phase breakdowns. Run `python scripts/estimate_task.py --task "<description>" --path "<codebase_path>"` to get structured estimates with risk factors and checkpoints before committing to work.

What factors does codebase analysis consider when estimating time?

Codebase analysis measures file count, lines of code, test coverage, and complexity markers to establish project scope. Combined with your task description, it produces estimates broken down by phase—analysis, implementation, testing, verification—so you understand where time concentrates and can plan sprints accordingly.

Can I use task estimation across different Python projects?

Yes. The estimation utility works on any codebase path you specify. It analyzes the target project's scope independently, so you can run estimates against multiple Python projects to compare task complexity and plan resource allocation across codebases.

What output does the estimation script provide?

The script returns a breakdown with time estimates, phase durations, risk factors, and checkpoint recommendations. Use the `--json` flag for structured output suitable for integration into planning tools or dashboards.

When should I run task estimation in my workflow?

Run estimation before starting non-trivial coding tasks. It reduces planning guesswork by giving you a realistic time window and clear checkpoints upfront, enabling better sprint planning and incremental delivery scheduling.