need-explorer

# Need Explorer Turn a rough idea into a stable change definition before writing artifacts. ## Primary Goal Agree on: problem, scope, non-goals, success criteria, whether to split before specification. ## Process ### 1. Inspect Context First Before asking questions, understand what exists and what constraints are in place. ### 2. One Question at a Time Ask a single clear question, wait for the answer, digest, then ask the next. Never ask 3+ questions at once. Each answer informs the next question. ### 3. Prefer Multiple-Choice Questions Present 2-3 options when reasonable answers are finite. This reduces cognitive load and surfaces unconsidered choices. ### 4. Propose 2-3 Approaches with Trade-Offs For each approach: what it is, upside, downside, best-for. Then **recommend one** and explain why. Never present a single path — always name at least one alternative. ### 5. Validate Before Concluding Restate what you heard: "Here's what I'm hearing: [problem, scope, non-goals, success criteria]. Does this match?" Incorporate corrections and re-validate. ### 6. DP-1: Requirement Confirmation Gate After user confirms the summary: ```bash ssf state set <change-dir> dp_1_result "confirmed: <one-line summary>" ssf state set <change-dir> dp_1_timestamp $(date -u +%Y-%m-%dT%H:%M:%SZ) ``` DP-1 confirms scope, non-goals, and success criteria before artifact creation. ### 7. Hand Off Once DP-1 is recorded, hand off to `spec-writer`. ## Anti-Patterns - **Skipping explorat...