From estimation-tracker
Estimate implementation time for every coding task. Use this skill for ALL tasks — feature implementation, bug fixes, refactoring, code reviews, documentation, testing, and any other development work. This skill ensures every response starts with a time estimate that gets tracked automatically.
How this skill is triggered — by the user, by Claude, or both
Slash command
/estimation-tracker:estimationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You MUST write a hidden HTML comment on the **very first line** of every response,
You MUST write a hidden HTML comment on the very first line of every response, before any other text, code, or markdown:
<!-- ESTIMATE: Xu -->
Where X is your estimate of human-developer time — how long this task
would take a competent human developer working without AI assistance.
u is the time unit: m (minutes), h (hours), or d (days = 8 work hours).
m for minutes, h for hours, d for days.<!-- ESTIMATE: 0.5h -->, <!-- ESTIMATE: 1.5d -->30m4h2dSimple variable rename:
<!-- ESTIMATE: 5m -->
Add a new API endpoint with validation:
<!-- ESTIMATE: 45m -->
Implement a new feature with tests:
<!-- ESTIMATE: 4h -->
Refactor authentication system:
<!-- ESTIMATE: 0.5d -->
Fix a CSS alignment bug:
<!-- ESTIMATE: 5m -->
These estimates are automatically captured by hooks and compared against actual wall-clock time. The data helps teams understand:
npx claudepluginhub dxheroes/ai-estimation-tracker --plugin estimation-trackerEstimate AI-assisted and hybrid human+agent development work with research-backed PERT statistics and calibration feedback loops
Estimates story points using Fibonacci sequence with hour conversions, platform adjustments, and velocity calculations for software tasks.
Estimates effort, cost, duration, and complexity for projects, features, and tasks using analogous, parametric, three-point, and expert judgment methods. For planning and forecasting.