Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why does what I asked for never match what gets built?

You can see the feature in your mind. You say it out loud, and it sounds complete. But the words you choose leave room — and someone else fills that room with their own guess, not yours. This is not a writing problem. It is a decision problem you have been leaving for someone else to make. Every gap in your spec is a choice you declined to make. Someone else made it instead, and now you call the result wrong. The fix is not more detail for its own sake. It is naming the decisions that matter: what counts as done, what happens at the edges, what the exact input and output look like. Do that, and the gap closes.

◆ How this problem reads on the two dials
GuidanceKnowledge
Coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
There is a real skill to teach — how a spec is structured — but the harder part is the discipline of actually deciding instead of describing, which only practice builds.
How the two dials adapt to you →
What’s really going on

The gap isn't in your skill — it is in your words. You described a feature, not a decision. Choose the ambiguity yourself, before someone else chooses it for you, wrongly. Write the exact inputs, the exact outputs, the edge cases, and what 'done' looks like. That is the job you've been avoiding.

🔒 What you’ll build togetherUnlock by starting
A moveWrite the exact input and the exact output for one real example — not a description, actual data.
A moveList three ways this feature could be misbuilt. Write a line in your spec that rules out each one.
A moveName what 'done' looks like in one sentence the builder could test against, not a feeling you'd recognize.
A moveFind the place in your spec where you wrote something vague because deciding felt tedious. Decide it now.
A moveRead the spec aloud to the builder before they start. Where they hesitate or ask 'what do you mean' — that is your gap.

What changes unlock by starting

  • Specs that get built right the first time, without three rounds of correction.
  • Less frustration re-explaining the same feature after it comes back wrong.
  • A working habit of deciding details instead of leaving them to chance.
  • Builders who trust your specs because they no longer need to guess.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.