swarm-speclisted

# swarm-spec — requirements phase Quality here is leverage: every later phase builds on this document. Expect the strongest available model — if this session runs a lesser tier, say so and let the user decide. ## Pick a planning mode first Requirements work isn't an interrogation — the goal is to **remove confusion and unstated assumptions**, not to make the user answer a hundred questions. Before diving in, offer how much to involve them (recommend **hybrid**; they can switch anytime): - **ask-each** — put every genuinely uncertain requirement to the user before locking it. Maximum control, slowest. - **recommend-all** — proceed on your recommendations/assumptions for *all* features, record each assumption, and surface them together for one batch review. Fastest. - **hybrid** *(default)* — ask on the high-stakes or truly ambiguous decisions; assume sensible defaults on the rest and log them. The user may also scope it ("ask me about auth and billing, assume the rest"). Whatever the mode, **every assumption is recorded** (in the question queue, status `ASSUMED`) so the closing summary can show exactly what you decided for them. ## Clarify, don't grill Only *decisions* go to the user; *facts* are looked up (codebase, vault, web). For each decision surfaced: **lead with a recommendation**, state the assumption behind it, list the alternatives, and accept any free-text answer. If something is only mildly uncertain and the mode allows, assume the sensible default a