Section 1 of 9
Ideal State
Knowing and Writing Down What You Want
Getting what you want out of your head and into one document, precisely enough that done is defined before anything gets built.
Why it matters when agents do the typing
Deciding what to build and what counts as done belongs to the people who need the result and will answer for it. An agent never sees the idea in your head, only what you captured, so every fact you left out becomes its guess. Even an executor that questions the target cannot know what you need better than you do, and no amount of code review fixes a wrong target.
The course: 5 lessons, about 47 minutes of reading, in the order below.
-
1.1
Articulating the Ideal State
Core 1 · Depth: do
Getting what is in your head into one written document an agent can build from and a stranger can check: ideal-state prose first, then constraints, dated decisions and criteria.
A mistake it teaches you to catch: A team switches to a larger model after an agent builds the wrong thing, when the prompt never stated the fact the build got wrong.
Lesson: Getting What You Want Out of Your Head 8 min
-
1.2
Framing the Problem
Depth: do
Working out who has the problem, what outcome would solve it, and what is deliberately out of scope, before any solution is on the table.
A mistake it teaches you to catch: A CSV export button with column pickers built for a request whose real need was the same monthly report sent to an accountant.
Lesson: The Problem Behind the Request 10 min
-
1.3
Requirements and Acceptance Criteria
Core 2 · Depth: do
Turning intent into specific, checkable statements of what the software must do and how well, so done has a definition before work starts.
A mistake it teaches you to catch: An export feature marked done that silently omits archived records, because no criterion said whether to include them.
Lesson: Writing Down What Done Means 10 min
-
1.4
Domain Modeling and Invariants
Depth: do
Naming the things in the problem, their lifecycles and the rules that must always hold, so code and tests can enforce them.
A mistake it teaches you to catch: A lifecycle modeled as scattered booleans (isPaid, isShipped, isCancelled) that allows impossible combinations such as shipped but never paid.
Lesson: Rules That Must Always Hold 9 min
-
1.5
Decisions: Recording Why, Inside the Living Artifact
Depth: do
Recording each decision as a dated entry in the project's one living ideal-state document, with the options, their costs and the reason, so later readers, human or agent, can tell a deliberate choice from an accident.
A mistake it teaches you to catch: A public API field named and shipped during a small bug fix, making the name permanent for every client.
Lesson: Writing Down Why 10 min
Section test: Ideal State
12 questions across the 5 lessons above. Take it after the course; each answer explains itself.