plan-swarmlisted

# Plan Swarm **Recommended model tier:** smart (opus) - this skill requires careful reasoning Structured planning interview to decompose work into independent stories before running a swarm. ## Quick Reference ``` plan swarm → Full interview workflow (recommended) plan swarm --fast → Skip interview, state assumptions, decompose directly ``` ## Workflow ### Phase 1: Understand Explore the codebase and existing context before asking questions. 1. **Read existing decisions** via `mcp__plugin_aide_aide__decision_list` and `mcp__plugin_aide_aide__decision_get` 2. **Search memories** via `mcp__plugin_aide_aide__memory_search` for relevant past context 3. **Explore the codebase** — read key files, understand architecture, identify boundaries 4. **Identify the scope** — what is the user asking for? What are the natural boundaries? Do NOT ask questions yet. Build understanding first. ### Phase 2: Interview Conduct 2-3 rounds of focused questions. Each round has 2-4 questions. Max 3 rounds total. **Round 1: Scope & Boundaries** - What is in scope vs out of scope? - What are the success criteria? - Are there any constraints (time, tech, compatibility)? **Round 2: Dependencies & Risks** - What shared state or files will multiple stories touch? - What could go wrong? What are the risky parts? - Are there external dependencies (APIs, services, data)? **Round 3: Acceptance Criteria** (if needed) - How will we know each story is done? - What tests shou