pre-build-soplisted

# Pre-Build Standard Operating Procedure ## Why this exists Agents default to writing code immediately. They pattern-match from memory, skip research, never look at real inputs, make a dozen unstated assumptions, and then patch bugs forever instead of admitting the initial approach was wrong. Every bug stacks on top of the wrong foundation. The work looks like progress. It isn't. the user pays for every hour of "making it look like it's working." This SOP replaces that default with a discipline: **no code until six steps are done.** ## Relationship to Constitution Part 13 (Signals Gap Law + Progression Law) This skill pairs with CONSTITUTION.md Part 13. Pre-build-sop governs PREPARATION discipline before building. Part 13 governs EXECUTION discipline after approval — including in-scope discovered work surfaced during prep. Together they close the full cycle: prepare completely, then execute completely. If a prep step surfaces work adjacent to the authorized task (a bug in a dependency, a missing test, a README that needs writing, an upstream issue worth filing), Part 13's Progression Law says execute it the same session with subagents — not "save for version two." Dismissal during prep is the same failure mode as dismissal during execution. The practical pattern: when you surface adjacent work during the six prep steps, name it in Step 5 (the plan), get the user's nod, then execute it as a subagent thread while proceeding with the main build. Do NOT present it as a me