From the "10 rules":

> Specific time estimates (minutes, not "a bit").

I actually wish the model would go completely in the opposite direction. Except in the rare circumstances where the model has actually measured something, it is hilariously deficient in its concept of time. It will often output phrases like "this relates to <thing> that you did weeks ago", referring to something that happened in the session just a few turns (and hours or a couple of days) ago. Likewise for estimating how long a coding tasks takes, it is hilariously inept. It honestly feels like it rolls two completely independent dice to select a number and a value from (hours | days | weeks) when it needs to attach an estimate to something. I'd much rather read "a bit" than be distracted by these utterly nonsensical times.

The full skill gives this example:

>Bad: "This will take some work." Good: "About 15 minutes if tests already cover this. An afternoon if not."

My experience is that it is very likely that whatever task this is describing takes anywhere from 1 to 30 minutes, consistently. Maybe I just work way faster than the average person.