Design Before Build — Stop Agents Coding the Wrong Thing

Forces four artifacts to exist before any implementation code gets written on a build: a plain-English technical design doc (user path, stack, edge cases, security, explicit out-of-scope list), an adversarial critique pass on that doc, a clickable HTML mockup gate for anything with a UI, and a 3–8 ticket breakdown detailed enough to hand off cold. For freelancers, the design doc doubles as a scope document — anything a client asks for later that isn't in it is a change order, not free rework. Sized to the job: one page for a landing page, no ten-page ceremony on a two-hour task. Repeat-use on every new build.

New in v3: an included checker script that fails the run on a missing section, an empty critique, the wrong ticket count, a missing mockup, or any implementation file written too early, plus a job-sizing rule (under 4 hours gets one page), a client-build security checklist and fill-in ticket and final-reply templates.