Read Before You Build.
The fastest way to make something clunky is to add a part you already have. Before your agent builds anything, it reads what's already there.
- What I askedIs it klugey?
- What it foundMost of it already there
- What it does nowReads first, builds the gap
Is it klugey?
Right after the car-wash conversation in Lesson 2, my advisor had started an agent working on that judgment system. I stopped and asked the question I should ask more often:
Now is this system that I've just added, and afterthought, is it unnecessary add on? Is it klugey? Is it clunky? And if not, if it's what we need, then what else are we missing?
Honest answer: the idea isn't an unnecessary add-on, but the way I briefed it would have made it kludgy. That was my fault, not yours. When I checked your spec v3 to answer you, I found it already holds most of a judgment system under other names: […] I briefed the lane before reading any of that, so it would have built a parallel system beside yours. That's exactly the klugey part. It's fixed: the lane now maps your spec first, marks each part covered, partial or missing, and proposes only what fills a gap, using your spec's own names. […]
↑ Spec v3 is the third version of my written design, and a lane is one agent's piece of the work. The trim is the list of what my design already had. A quarter of an hour later, about this very course:
[…] On the course: I did it again. That's the third time today. I wrote you 15 lessons without first reading Gonna Is Fine. […]
It had drafted lessons for this course before reading the thirty in my first one, and about half were already there. This course was written the other way round: all thirty lessons of course 1 first, then the plan.
Reading feels slower than writing.
Agents are eager builders. Writing something new feels like progress, and reading what's there feels like a delay. So an agent asked to add a feature will often add a whole new part beside one you already have, with a new name, slightly different rules and twice the upkeep. That's what klugey means: bolted on, not built in.
My advisor caught it only because I asked. When it finally read my design, it found most of what I'd asked for already there, under other names. The agent it had sent would have built a second copy.
Map it first.
Before any new piece, the agent writes a short map with three kinds of entry:
Covered.
What already does this job, and where it lives.
Partial.
What does some of it. Usually that's where the new work belongs, as an addition, not a twin.
Missing.
What really isn't there. Only this gets built, and it uses the names you already use.
Course 1's Lesson 19, Trust the Note, Then Check says “Read first. Check second. Build third.” That lesson is about picking up someone else's notes before you carry on. This one is about adding to a system: read the system before you add to it. You'll see covered, partial and missing again in Lesson 6, because they work for any claim about what exists.
Read what's there before you add to it.
Before any new piece, the agent maps what already does the job, what partly does, and what's really missing, with where each lives.
It builds only the gap, using the names you already use.
Make it read first.
One paste for the next time you add anything, and one question for after.
- Give your agent the rule.
Paste it at the start of any job that adds something new.
Before you add anything new, read what we already have. List what already does this job, even partly, and where it lives. Mark each part covered, partial or missing. Then propose only what fills a real gap, using the names we already use. Don't start building until I've seen the list. - Ask the klugey question.
After anything new gets added, ask: is this an unnecessary add-on? Is it clunky? And if it's what we need, what else are we missing? It's my question, and you're welcome to it.
Read first, then build only what's missing. Otherwise you pay to build it twice.
Where this comes from in course 1. Course 1's Lesson 19 (read the notes before carrying on) and Lesson 20 (keep your rules in one place). New here: reading the existing system before adding to it, mapped as covered, partial or missing.
Prove It's Missing
“It's not there” is the easiest claim to get wrong. It needs the search, and the same search finding something you know is there.
← Previous: Lesson 4, Don't Let It Shrink the Ask
Every exchange on this page really happened and is quoted exactly, slips included; […] marks where I trimmed. Times are Eastern. Names of clients, people, companies and products are left out. My agents are AI models; the names are left out on purpose.