slipway-intake-clarificationlisted

# Intake Clarification ``` IRON LAW: NO PLANNING WITHOUT CLEAR INTENT ``` ## Purpose Clarify user intent, define scope boundaries, and produce an approved summary before planning begins. Mitigates scope ambiguity, intent drift, and over-scoping. ## Process ### 1. Read Context Use `slipway next --json` for the current state and governed bundle path, then read `intent.md`. Carry this scope posture while reading: - surface the unspoken assumption before the next question - prefer one well-targeted question over scattered batches - do not move to planning until the approved summary names both what is in and what is out ### 2. Assess Complexity Use `## Complexity Assessment` to set question depth: - **trivial**: 1-2 quick confirmation questions - **simple**: 2-3 scope and acceptance questions - **complex**: 3-5 scope, constraints, dependency, and risk questions - **critical**: 5+ questions plus guardrail-domain and constraint checks ### 3. Clarification Loop (one question at a time) For each clarification round: 1. Read the current state of intent.md 2. Identify the most important unresolved aspect 3. Ask ONE focused question to the user 4. Update intent.md with the user's response in the appropriate section 5. Repeat until all required sections have substantive content **Required advancement sections:** - `## In Scope`: concrete files, APIs, commands, or user-visible surfaces - `## Out of Scope`: at least one explicit exclusion - `## Acceptance Signals`: at least one veri