Production activity
Everything built with SpecBox, in figures.
Aggregated counts from every board in the ecosystem, with nothing per person or per project. With their date and method, including what doesn't flatter us.
Snapshot from 2026-10-04 21:29 UTCHow we measure each figure
SpecBox is built with SpecBox
2,510 use cases. Each square is one.
Everything on the ecosystem's boards: what's done, what's waiting for review, what's in progress and what's still queued. No rounding.
- projects
- 31
- developers
- 18
- stories
- 503
- acceptance criteria
- 10,077
- use cases done
- 80 %
- Done2,011
- In review47
- In progress44
- Queued408
Snapshot from 2026-10-04 21:29 UTC· Aggregated data, no personal information; archived ones are left out.
Speed that survives review
Use cases closed, week by week.
Each bar is the use cases that moved to done that week, across all projects. We publish the slow weeks too.
No delivery data yet.
North star metric
0% of closed use cases have their full evidence and were accepted by a person.
The figure that says whether SpecBox delivers on its promise: not how much gets closed, but how much of it has receipts that prove it and a person who signed it off. We publish it even when it doesn't flatter us.
How it's measured- use cases closed since 2026-10-04 21:12 UTC
- 3
- with full evidence
- 3
- accepted by a person
- 0
Method
How we measure each figure.
Everything comes from a public view of the SpecBox Cloud database that counts every native board at query time.
- Projects, developers, stories, use cases and criteria
- The total count at query time across every board, including test boards and our own.
- States
- The current state of each use case. Archived ones are counted separately: they're left out of the mosaic and the percentage.
- Pace
- Use cases whose closing falls in each week (Monday to Sunday, UTC) over the last eight. The last one may still be in progress, and a reopened case counts in the week of its last closing.
- North star metric
- Use cases closed since 2026-10-04 21:12 UTC, the day the panel launched the «Accept» button. Full evidence: every visible criterion is done and has a passing receipt. Accepted: the project's owner or an admin accepted it in the panel; a session verifying a criterion doesn't count, even if a person signs it. If a criterion is undone or the use case reopens, the acceptance voids itself.
- People
- We never publish anything per person or per project: only aggregates.
What we don't publish yet
We've committed to publishing six metrics almost nobody publishes. Today you have the counts, the pace and the north star metric; these will come once we measure them with the same care:
- 1How often hooks block per session and how many blocks end in a useful fix.
- 2The token cost of each use case and each criterion.
- 3The review time of each PR.
- 4How many extension installs get activated and how many remain after 30 days.
- 5How many projects are abandoned, how many reach production and how often work is handed over.
Let your agents prove what they did.
Install the extension, open Claude Code and start with /discovery. The first receipt arrives with the first closed criterion.
Or from the VSCode command palette:ext install EmbedBuild.specbox-engine