designlisted

# Design **Feature:** "$ARGUMENTS" ## Phase 1: Architecture ### 1.1 Validate Input + Read Ideation Require a feature description; ask if missing. Check for `plans/<slug>-ideation.md`. If present, read it (output of `ideate`: problem, prior art, alternatives, concept, constraints) and use as foundational context. If absent, ask: "No ideation file. Run `ideate` first, or proceed without prior-art search?" ### 1.2 Shared Exploration Wave Dispatch 5 `code-explorer` agents in parallel, one per **dimension**: - **Architectural fit**: existing patterns, abstractions, conventions - **Touchpoints**: files, modules, integration points crossed; data flow boundaries - **Risks & dependencies**: what could break, coupling, sequencing constraints, fragility - **Constraints**: performance, security, backward compat, observability - **Failure modes**: how the user-facing problem manifests (completion / abort / drop / crash); per mode: trigger, state, what the user sees. From logs/observations, not just code paths. Each explorer writes findings to `plans/<slug>/.workspace/exploration/<dimension>.md` and returns: 1-paragraph overview + path + top 3 headlines + 5-10 essential files. Prior art belongs to `ideate`, not here. ### 1.2.5 Synthesize Shared Context Coordinate the 5 outputs into a 1-2 page document: per-dimension highlights, deduped essential files (~15-20), cross-dimension findings, **failure-mode coverage table** (per mode: covered today? if not, what's needed). Architects