Estimate in agent-hours, not team-weeks
When the spec is tight, the build is the short part.
The old reflex: someone describes a feature and I hear “a few weeks.” That number comes from human teams — handoffs, standups, context switching, waiting on review.
With a coding agent and a well-defined spec, a working app lands somewhere between thirty minutes and six hours. The bottleneck moved. It's no longer typing; it's how clearly I can describe the thing.
So I estimate in two parts: the time to write a spec I could hand to a stranger, plus agent-hours. If I can't write the spec yet, the honest estimate is “unknown” — not “weeks.”
[ADD A REAL EXAMPLE — e.g. how long the first Captain's Chair build took]
┌─ RULE OF THUMB ──────────────┐ │ │ │ spec unclear → estimate ? │ │ spec clear → agent-hours │ │ unknowns → ask first │ │ │ └──────────────────────────────┘
The useful part of the reframe isn't the speed. It's that “how long will it take?” becomes “how well do I understand it?” — and that second question has an answer I can work on today.
[ADD — what you'd tell someone running their first agent build]
$ diff old-habit.txt new-habit.txt - estimate = gut feel × team velocity + estimate = spec time + agent hours