PoCcorn

One message to Claude Code on a Saturday morning. Not a spec, a paragraph: what I wanted, plus one rule. Run an adversarial review at every step, and write a rubric wherever one is missing. About 55 minutes later: product doc, spec, review rubrics (product, design, engineering, security, trust and safety), GitHub sign-in, PoC pages, portfolios, moderation with a hold on first submissions, share cards. 51 tests and 21 browser smoke checks, all green. What it nailed: the plumbing, and running its own review loop. 9 review runs, 76 findings, 11 blockers, all fixed. Where it struggled: it wrote "never run migrations in the build" into the spec, then put exactly that in package.json. A separate reviewer, with no memory of writing the spec, caught it. Two smoke checks were hard-coded to pass; making them real exposed a race. Fresh context beat clever context. Then Pareto kicked in. The first 80% took an hour. The last 20% took an additional half-day: name, domain, OAuth app, database, DNS, mail, launch posts. None of it code, all of it needing me, my opinions and my credit card (for the domain). 11 messages from me in total: 1 built the app, 10 were decisions and account chores. Kill date set before launch: by 15 November, 25 builders, 15% referred by another builder, or I park it.