Command
Estimate Task
Estimates a task by inspecting the code it touches, then gives an hour range with assumptions and the unknowns behind it.
11. Identify the likely entry points with search. List the files and functions that would change.
22. 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.
33. 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`).
44. 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.
55. Add the unknowns: anything you could not read, external services, missing specs, decisions owed by others.
Claude CodeCodex
Estimate Task
CommandWorkflow
Free