Talk it through with Aurelius
Why do my specs miss edge cases and the reasons behind them?
You can write a spec. The format is right, the sections are there. But someone asks why you chose this path over that one, or what happens if the input is empty, and you go quiet. This is not a gap in your training. It is a habit of stopping at the first answer that works. You write the case you already pictured, then call it finished before you ask what you didn't picture. The fix is not a course on edge cases. It is a question you ask yourself every time, before anyone else asks it for you.
◆ How this problem reads on the two dials
GuidanceKnowledge
1:1 with AureliusWith others (a Pod)
This is less about new facts and more about building the habit of interrogating your own work, so coaching carries the weight.
How the two dials adapt to you →What’s really going on
The gap isn't skill — it's that you write what you already see, and stop. Edge cases live where you haven't looked yet. Choose to ask "what breaks this?" before you call it done. The why is not decoration — it is the test you skipped.
🔒 What you’ll build togetherUnlock by starting
A moveBefore you submit any spec, write down three ways it could fail — not think them, write them.
A moveFor every decision in the spec, write one sentence on why you chose it over the alternative.
A moveHand the spec to someone and ask them to attack it for ten minutes before you call it finished.
A moveKeep a running list of edge cases you missed after the fact, and review it once a month.
A moveWhen you write 'the system will X,' stop and ask 'what if it can't?' Answer it in the same paragraph.
What changes unlock by starting
- You catch edge cases before a reviewer finds them for you.
- You explain your reasoning in meetings without hesitating.
- Your specs need fewer rounds of revision.
- People trust your specs enough to build from them without asking you first.
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.