Back to 1999: requirements first
This is how we review our code: we pour the effort into requirements first, review them before any code, then iterate on milestones like everything else. It is time to learn systems analysis and design again.
The reason is mechanical. The more requirements you have, the more of the loop closes, so that nothing is left to a guess. That is what gets you slopless code.
Where this comes from
Measured On Unreal Engine’s SemVer parser the requirements were written first, from the public Semantic Versioning 2.0.0 spec: 16 requirements, every numbered rule mapped to one or excluded with a reason. Writing them against the code found 4 faults that fail when run, before any break was made, and 7 of the 16 have no test about them. See on code you can read for yourself. The requirements and the reading found those faults; the breaks add the count of what no test holds.
It extracts new requirements from the ones you have
The tool automatically extracts requirements from existing requirements. You do not list them by hand. It walks each use case step by step: every step needs something to be true, and when no requirement provides that, the chain has inferred one nobody wrote. It is marked inferred and goes to the owner as a question, because only the owner can decide it. See testing raw for what that found on SemVer.
Complete in, accurate out
The more complete the requirements, the more accurate the prompt built from them: an agent acting on them has less to guess. Which ones you write first matters as well, so start with the ones that run through the most code (seed it first).
Where two features meet
A large new feature often joins features you already have. We expected the walk to find the gaps where two such features meet, because each side’s requirements are already tested. We tried it once, on two features of our own game, and it does not: joined, the walk asked no new question, and an agent reading both models named places the graph missed and found real faults neither model states. No count is given because the pair is not public.
Why the graph misses them: only sets and branches make an edge to a name, so two requirements that call or read the same thing do not meet, and neither model says what it offers the other. It would take three things, none of them built: calls and reads as edges, each model declaring what it offers and what it takes, and a check that compares the two lists.
Open One pair, and not blind: the second feature was built as a clone of the first, both documents name code classes, and the agent had read one model first, so the reading number is an upper bound. Whether to remix rather than invent was not measured, and remixing with zero errors was not shown. That more complete requirements give more accurate prompts is our judgment from building with it; no run has measured it directly.
Made by RJ’s TNT Tools. TNT Tools’ own work, not a Heavy Iron product.