Agent-estimate, how long a coding task takes, at agent speed(github.com)

Estimating in "agent hours" sounds clever until you try to roll it up across a 12-person team and half the tickets are blocked on review, infra, or someone clarifying the spec. The bottleneck stopped being keystrokes a while ago, so optimizing the metric that measures keystrokes feels like it misses where the time actually goes.

switched our sprint points to agent-hours last quarter, surfaced bottlenecks fast