The argument
For thirty years the scarce thing in software was hands: who could actually write it. That constraint is gone, and it did not take the problem with it. What sits in its place is harder to buy. What is worth building, in what order, to what standard, and how you know when it is genuinely finished.
The second-order effect is the part most people miss. Building fifty times faster does not shrink the work, it multiplies the surface competing for a fixed amount of attention. More capacity makes selection and sequencing more decisive, not less. Everyone gets the capacity. The gap between capacity and judgment is now the whole game.
What the gap is made of
Each one below is a way projects fail now that they did not fail before, the scar it left on mine, and the instrument I built so it cannot happen the same way twice. The instruments are open source. The links go to the thing itself, not a description of it.
Ten questions asked at four moments in a task, chosen because they are the ones the request did not contain. The expensive builds are rarely botched. They are flawless executions of a brief nobody examined.
Every rule written as the thing that went wrong first, with the month it cost something and the mechanism that now stops it. A principle without its scar is advice. With it, it is a decision you can hand to someone else.
The stranger's first five seconds, simulated before the thing ships, on the half a build gate cannot measure. A weekly health check is not monitoring, and a page you wrote is not a page anyone can read.
Find where caution has been quietly written into the code as a stub, a refusal, or a fabricated success. Paired with philosophy/, which names the tilt behind the reflex instead of treating each instance as a surprise.
A four-rung ladder: built, deployed, works, fed. You say which rung you have actually proven and what the proof was. Its companion, the seven cheap lies, is the list above, so the same check cannot fool the next person.
Check it yourself
The whole set runs inside your own Claude, on your own project, in one command. It will start correcting you tonight, without me in the room. That is the honest test of whether any of this is real.
/plugin marketplace add Traviseric/best-practices /plugin install best-practices@traviseric
What is deliberately not in it: the overnight autonomous runner, the goal-sheet system that decides what agents work on next, fleet-scale worktree discipline, and the Business Brain. Those need the operating system around them to transfer, so they live in the course and in the work itself. The free tier is the part that survives without me.
Where this goes
The instruments above, installed into your agent. Yours, with no conversation required. Most people never need anything past this.
The operating system the instruments came out of, run end to end on a real project: verifiers, concurrency, overnight runs, and how a brief gets chosen.
Judgment applied to your particular thing. Which of your fifty possible builds is next, structured so it holds, and finished to the rung where a stranger can use it.
The third one is the part that does not compress into a repository, because it is not a method, it is a decision about your business. If you have the capacity and suspect it is going into the wrong things, that is the conversation worth having.