Cycle time at p50, p75 and p90, not a flattering average. An agent can read every number over MCP.
The average describes no card you have. The tail is where the truth is.
0184 cards finished in 90 days. Median 1.6 days
Cycle time runs from created to done. You get the average beside p50, p75 and p90, so the slow tenth cannot hide in a mean.
| Metric | Hours | Days |
|---|---|---|
| Average | 62.4 | 2.6 |
| p50 (Median) | 38.4 | 1.6 |
| p75 | 74.4 | 3.1 |
| p90 | 153.6 | 6.4 |
One card in ten took four times the median, or more. The mean says 2.6 days.
02Kai Holt added a label to WEB-119, two weeks after it shipped
Finished work is dated by when it finished, never by when the card was last touched. Edit or archive it later and it stays in the week it shipped.
12 Aug 17
WEB-119 finished
Counted once
9 Aug 24
7 Aug 31
WEB-119 label added
Stays in Aug 17
Touched two weeks later. Still counted in the week it shipped.
0311 issues finished this week
Throughput counts what finished in each ISO week. Velocity lays the last twelve weeks side by side.
04Cycle 14, day 12 of 14: 6 left
What is left against the days gone, for a project over 30 days or for one cycle over its own dates.
05Lena Park holds 7 open issues
Open issues on each assignee, people and agents on the same chart.
18 open. Lena holds more than both agents together.
06You moved cycle time to the front and exported a PDF
Reorder the charts and hide the ones you do not read. Filter to a project, then a cycle.
Export CSV JSON PDF
07claude-build read cycle time for the last 90 days
Every measure is also a read-only tool. Ask the agent you already use how the cycle is going.
Lena Park asked claude-build
How long does a card take us these days?
claude-build replied
Half finish within 1.6 days. One in ten takes more than 6.4.
The coordination layer for humans + AI. Free SSO on every plan, no per-seat SSO tax.