designlisted

# Design — propose-then-critique → designs/<slug>.md draft ## AUDIENCE Skill body ∈ SPEC-ADJACENT ∴ glyph register. Design file output (`designs/<slug>.md`) ≡ user-reviewing surface pre-spec-fold ∴ steno register (readable symbols `→ & | §`, ⊥ heavy math glyphs `∀ ∃ ∴ ⊥ ∈ ∉`). Encoding follows audience. ## Position in funnel `/sdd:design` ≡ front door — caller has named the layer mentally ∧ wants to commit a shape. If layer / shape-space unclear, run `/sdd:explore <topic>` first (optional pre-step → tradeoff matrix @ `designs/<slug>-explore.md`); user picks an option, then dispatches `/sdd:design <option>` to commit shape. No auto-route — user-driven only. ## Loop 1. read `SPEC.md` ∈ root → degrade gracefully if absent 2. topic vague ∨ empty → ≤ 2 questions to localize, then propose 3. propose shape (named structures, types, key decisions) ∈ 1 pass 4. surface `## Open Questions` list at bottom 5. wait → user critique / answers 6. update Proposal in place; resolved Qs → `## Design decisions` w/ rationale 7. repeat 5–6 until `## Open Questions` ∅ 8. on confirm → write draft to `designs/<slug>.md` (steno-encoded per template) ∀ turn: ⊥ self-resolve Open Questions. resolution ⊢ user input. ## Distinction from socratic |skill|converges on|mechanism| |socratic|"enough"|1 question/turn, sharpen intent| |design|"exhausted"|propose shape, exhaust open Qs| ⊥ merge. socratic = bug ∨ small-feature framing. design = structural choice. ## Output template (design file body) body