Retrofit
Applying structure to a project that’s already a mess — without pausing shipping.
Why retrofit beats rebuild
You have a project. It’s been running for months. There’s no CLAUDE.md. The agents (if you have any) are vaguely defined. Decisions live in chat history. Notes are scattered. Things break and get fixed without postmortems. The project ships, but the operating layer underneath it is invisible.
The instinct is to pause and rebuild. Stop work for two weeks, install everything correctly, then resume. Almost always wrong. 80% of rebuilds fail — the project loses velocity, the rebuild has its own bugs, the team morale tanks, the original work still isn’t shipping correctly. The pause didn’t justify itself.
The right shape is incremental retrofit while shipping continues. One piece at a time. ~2 hours each. The project keeps shipping the entire time. Three pieces in 30 days is realistic; that’s a 30-day plan that succeeds 80% of the time vs the rebuild’s 20%.
This lesson is the 30-day plan. The triage that picks the first piece. The discipline that makes the second piece earn its way in. The rule that prevents you from over-installing structure that doesn’t fit your work.
The five-month story
Five months into Quantum Caddy I had no CLAUDE.md, no sprint contracts, no postmortem template. Decisions were buried in chat. Agents were one-and-done. The project was shipping — slowly, with regular regressions — but the operating layer was invisible.
I tried the rebuild first. Two-day pause, drafted a vault structure, installed agents, wrote a CLAUDE.md for every venture. Day 3 I went back to actual work. By day 7 most of the structure was unused — I’d configured it cold without knowing which parts I’d actually use, and the new structure didn’t fit my workflows because I’d guessed at the workflows.
The pivot: retrofit one piece at a time, prove it sticks for 7 days, then add the next. CLAUDE.md week 1. Sprint Contracts week 2. Postmortem template week 3. By the end of the month I had three disciplines actually being used — not seven that existed but lay dormant.
The compound effect across months: those three early pieces produced the conditions where every subsequent retrofit (Memory architecture, Hooks, Vault structure, Wiki synthesis) had a place to fit. Big-bang rebuild would’ve produced none of that.
The rest of Expert · Lesson 01 is for subscribers.
Retrofit — applying structure to a project that's already a mess
- Every Expert-tier lesson — diagnostic prompts, transcripts, prompt kits, full homework
- Every research paper — methodology, figures, tables, reproducibility appendices
- New Expert lessons + papers as they ship (quarterly cadence)
- Foundations + Operating lessons stay free; bundles on GitHub stay free; this tier is the deep stuff
Free while the early catalog ships. Paid tier comes later — subscribe now and you’re grandfathered in.