shapinglisted

# Shaping ## Overview **Core principle:** Resolve unclear intent and consequential design choices *before* building. The cheapest place to fix a design is in conversation; the most expensive is in code you've already written. Shaping is where you subtract features, choose an approach, and establish a shared direction. ## The Decision Gate ``` NO CODE WHILE A MISSING CHOICE WOULD MATERIALLY CHANGE THE RESULT ``` Do not guess through material ambiguity. But do not invent ambiguity either: an explicit request to implement a clear, bounded change supplies intent, and a previously approved design stays approved. In those cases, skip shaping and continue with planning or implementation. ## Classify, and Announce It State the path out loud so the human can correct you. Complexity only *upgrades* the path. - **Spike** — "can this even be done?" → shaping is one line: state the question, then go probe (**spike-and-stabilize**). - **Bounded but unclear** — a contained change with one material uncertainty → resolve it briefly, record the result, then build. - **Bounded and explicit** — the request already pins down the result → shaping is unnecessary. - **Architectural** — new system, real choices → the full dialogue below, ending in a written design and the **planning** skill. ## How to Shape 1. **Ask only questions whose answers change the result.** Ask one at a time. A wall of ten questions gets skimmed and half-answered. Prefer multiple-choice when the options are gen