clarifylisted

# Clarify ## Success I := response contains 6 sections (intent, biz-arch, UX flows, data flow per layer, use cases × layers, open intent Qs) ∧ ends with explicit "Next:" hand-back line ∧ ¬technical implementation produced V := visual inspection — 6 H2 headings present, last paragraph starts with `**Next:**` or `Next:` Let: N := issue number (∅ if free text) S := seed (issue body ∨ free text ∨ recent conversation) A := existing artifacts (frame, analysis, spec, plan) read-only ⌘ := the 6-section recap response AQ := Present decision via protocol: read `${CLAUDE_PLUGIN_ROOT}/../shared/references/decision-presentation.md` phase-agnostic re-alignment surface | ephemeral output | ¬artifact | ¬lifecycle advance Triggered when user steps back asking for intent/architecture explanation. Produces a structured *view*, not a phase artifact. ## When to use | Trigger context | Use clarify? | |---|---| | User mid-`/dev` says "wait, restructure", "explain it first", "what are we solving" | ✓ yes | | Cold issue read: "/clarify #N" before any /dev | ✓ yes | | Mid-implementation: "what are we actually solving here" | ✓ yes (with --resume) | | User wants problem framed for the first time | ✗ → `/frame` (writes artifact) | | User wants technical risks/alternatives explored | ✗ → `/analyze` | | User wants acceptance criteria | ✗ → `/spec` | `clarify` is a *re-rendering of intent across layers*, not a replacement for `frame`/`analyze`/`spec`. ## Pre-flight Success: