Skip to content

commandWorkflow

Estimate Task

Estimates a task by inspecting the code it touches, then gives an hour range with assumptions and the unknowns behind it.

npx workspacetemplates add estimate-task --tool claude-code

Writes 1 file to .claude/commands/

.claude/commands/estimate-task.md14 lines · 1.2 KBFile
---
description: Estimates a task by inspecting the code it touches, then gives an hour range with assumptions and the unknowns behind it.
argument-hint: "<task or ticket text>"
---

Estimate this task from the code, not from the title: $ARGUMENTS

1. Identify the likely entry points with search. List the files and functions that would change.
2. Measure the blast radius: how many callers, imports or routes use them (use grep counts), whether there are migrations, public APIs or shared components involved.
3. Check safety nets: test coverage around those files, whether CI runs them, how old and how often changed they are (`git log --since=1.year --oneline -- <path> | wc -l`).
4. Break the work into pieces: implementation, tests, migration or data work, review fixes, deploy and verification. Give each a best and worst case in hours.
5. Add the unknowns: anything you could not read, external services, missing specs, decisions owed by others.

Output: total range (for example 6 to 14 hours), confidence (low, medium or high), a table of pieces, the assumptions, and the top two things that would blow the estimate. Do not pad the number with a hidden buffer; show any buffer on its own line. Change no files.

What it does

Estimates made from a ticket title are guesses. This command opens the files the task would change, counts what depends on them and checks how well they are tested before giving a number.

The answer is a range with a stated confidence and a list of assumptions, so the person asking sees what could move it.

Example

you › /estimate-task add SSO login for the admin panel

agent › Range: 14 to 30 hours, confidence medium. Auth lives in one module (lib/auth) with 9 callers and good tests. Unknown: whether the identity provider needs SCIM. Biggest risk: existing local accounts must link to SSO users.

Questions

Is the number a commitment?
No. It is a range with assumptions, meant to start a conversation about scope.
Can it estimate work in a repo it has not seen?
It needs to read the code. Without access it says so rather than inventing a figure.
  • Debug Error

    CommandWorkflow

    Free
  • Explain Code

    CommandWorkflow

    Free
  • Plan Feature

    CommandWorkflow

    Free
  • Reproduce Bug

    CommandWorkflow

    Free