1,079 stories.
2,917 chunks.
3.2M lines.
A development harness I built for myself, and what it shipped over 90 days. Every chunk validated, every cycle gated, every story carried through.
Same discipline. Different reps.
Craft is the harness behind these numbers.
10.9× more output. Same person, same hours. It's the planning loop, chunk validator, and agent team that made it happen. Open source.
Open source · Coming in JuneVolume shipped
3,226,724 lines changed · 2.56M insertions · 670K deletions · across 2,916 commits in 90 days. Code, content, configs, design tokens, infrastructure - everything that gets shipped through the harness.
Top 5 single-project pushes
Lines changed by one project on one day
The Operating Pattern
2,551 lines/day before craft.
27,818 lines/day after.
Same person. Same hours. The harness arrived Feb 1 and the daily output went up 10.9×. Pre-craft (Oct → Jan): 191K lines across 75 active days, one project at a time. Post-craft (Feb → May): 2.39M lines across 86 active days, up to 6 projects in parallel. The chart speaks for itself.
Milestones
Personal records
Building the harness
70,000+ lines
poured into craft in April alone.
While the harness shipped work across 17 projects, the harness itself kept evolving. April was the heaviest upstream investment month - the chunk-validator agent, batch planning, the alignment loop, design tokens, the Docs Command, the planning command. All shipped while everything else kept moving.
Note on the commit pattern shift: On Apr 9, craft started doing "one commit per story" instead of one-per-chunk. That's why the daily commit count chart looks calmer recently - each commit just contains more. Lines changed is the metric that shows the real intensity.
Activity
Rhythm
Monday peak. Saturday and Tuesday clear the "even" bar - you ship weekends.
7pm peak. 3pm secondary spike. 19.8% after-hours.
How the harness learns
Every problem solved here flows back to the center. Every project benefits from the next one's friction. The exponent isn't claimed - it's recorded in the wikilinks.
A flood of small bugs in one project sprint - too tiny for stories, too persistent to ignore. Distilled into one command.
174 invocations. Every project benefits.
7 of 22 fixes in a single sprint were design-fidelity loss. Tokens approximated, gradients off at small sizes, strokes breaking at 64px.
Now every chunk is checked against the spec at every variant size.
A browser tool was burning 114K tokens per QA task. Rewrote it as a thin skill + persistent playwright session.
4× cheaper. Powers QA in every project.
A schema migration silently dropped production data. The lesson became a validation gate.
Hasn't happened twice.
A mobile UX bug slipped past every validation. The audit got encoded as a risk tag on every UI chunk.
Caught before merge across all UI projects since.
CSS state-transition gaps shipped broken animations. Now flagged as risk tags.
Animation chunks get extra eyes before merge.
Every problem solved here flows back to the center. Every project benefits from the next one's friction.
That's the exponent.
Same discipline. Different reps.
Craft · 90 days · May 5, 2026
Craft is a Claude Code plugin behind these numbers.
Planning loop, chunk validator, agent team. Open source.
Open source · Coming in JuneSame person. Same hours. The harness arrived Feb 1 and the daily output went up 10.9×. Pre-craft: 191K lines across 75 active days. Post-craft: 2.39M lines across 86 active days, up to 6 projects in parallel.