clarify

# /clarify — Adaptive Requirements Clarification ## Chain (MUST) | Previous | Current | Next | |----------|---------|------| | Session start | /clarify | EnterPlanMode() → /implement | ## Core Model ``` /clarify → Measure complexity → Clear enough? ├─ Yes → EnterPlanMode() └─ No → Deeper clarify (explore, analyze, DRAFT...) → Re-measure → Repeat ``` Exit condition: **"Is this enough info to implement?"** --- ## Step 0: Route — Complexity Assessment Measure complexity internally upon receiving request (do not expose to user). ### Complexity Signals | Signal | LOW | HIGH | |--------|-----|------| | Request length | Short and specific | Long or ambiguous | | Keywords | "add", "fix", "change" | "design", "migration", "from scratch" | | Uncertainty | None | "not sure", "how should I" | | Impact scope | Single file/module | Cross-cutting, multiple services | | Risk | Low (UI, text) | High (DB, auth, breaking API) | | Existing patterns | Clearly exist | None or unfamiliar stack | - **LOW** → Shallow Path (completed within this file) - **HIGH** → Deep Path (see `deep/DEEP.md`) - **Ambiguous** → Start Shallow, monitor escalation conditions --- ## Shallow Path (Low Complexity) Remove ambiguity via quick Q&A, generate minimal specs, and enter Plan Mode. ### Execution 1. **Record**: Log original request + identify ambiguous parts 2. **Question**: `AskUserQuestion` (spe...