Swarm Planner

1---2name: swarm-planner3description: >4  [EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel5  multi-agent execution.6metadata:7  invocation: explicit-only8---9 10# Swarm-Ready Planner11 12Create implementation plans with explicit task dependencies optimized for parallel agent execution. This skill can be ran inside or outside of Plan Mode. 13 14## Core Principles15 161. **Explore Codebase**: Investigate architecture, patterns, existing implementations, dependencies, and frameworks in use.172. **Fresh Documentation First**: Use Context7 for ANY external library, framework, or API before planning tasks183. **Ask Questions**: Clarify ambiguities and seek clarification on scope, constraints, or priorities throughout the planning process. At any time.194. **Explicit Dependencies**: Every task declares what it depends on, enabling maximum parallelization205. **Atomic Tasks**: Each task is independently executable by a single agent216. **Review Before Yield**: A subagent reviews the plan for gaps before finalizing22 23## Process24 25### 1. Research26 27**Codebase investigation:**28- Architecture, patterns, existing implementations29- Dependencies and frameworks in use30 31### 1a. Optional: Stop to Clarification Questions32 33- If the architecture is unclear or missing STOP AND YIELD to the user, and request user input (AskUserQuestions) before moving on. Always offer recommendations for clarification questions.34- If architecture is present, skip 1a and move onto next step. 35 36### 2. Documentation37 38**Documentation retrieval (REQUIRED for external dependencies):**39 40Use Context7 skill or MCP to fetch current docs for any libraries/frameworks or APIs that are or will be used in project. If Context7 is not available, use web search.41 42This ensures version-accurate APIs, correct parameters, and current best practices.43 44### 3. STOP and Request User Input45 46When anything is unclear or could reasonably be done multiple ways:47- Stop and ask clarifying questions immediately48- Do not make assumptions about scope, constraints, or priorities49- Questions should reduce risk and eliminate ambiguity50- Always offer recommendations for clarification questions.51- Use request_user_input or AskUserQuestion tool if available. 52 53### 4. Create Dependency-Aware Plan54 55Structure the plan with explicit task dependencies using this format:56 57#### Task Dependency Format58 59Each task MUST include:60- **id**: Unique identifier (e.g., `T1`, `T2.1`)61- **depends_on**: Array of task IDs that must complete first (empty `[]` for root tasks)62- **description**: What the task accomplishes63- **location**: File paths involved64- **validation**: acceptance criteria65 66**Example:**67```68T1: [depends_on: []] Create database schema migration69T2: [depends_on: []] Install required packages70T3: [depends_on: [T1]] Create repository layer71T4: [depends_on: [T1]] Create service interfaces72T5: [depends_on: [T3, T4]] Implement business logic73T6: [depends_on: [T2, T5]] Add API endpoints74T7: [depends_on: [T6]] Write integration tests75```76 77Tasks with empty/satisfied dependencies can run in parallel (T1, T2 above).78 79### 4. Save Plan80 81Save to `<topic>-plan.md` in the CWD.82 83### 5. Subagent Review84 85After saving, spawn a subagent to review the plan:86 87```88Review this implementation plan for:891. Missing dependencies between tasks902. Ordering issues that would cause failures913. Missing error handling or edge cases924. Gaps, holes, gotchas.93 94Provide specific, actionable feedback. Do not ask questions.95 96Plan location: [file path]97Context: [brief context about the task]98```99 100If the subagent provides actionable feedback, revise the plan before yielding.101 102 103## Plan Template104 105```markdown106# Plan: [Task Name]107 108**Generated**: [Date]109 110## Overview111[Summary of task and approach]112 113## Prerequisites114- [Tools, libraries, access needed]115 116## Dependency Graph117 118```119[Visual representation of task dependencies]120T1 ──┬── T3 ──┐121     │        ├── T5 ── T6 ── T7122T2 ──┴── T4 ──┘123```124 125## Tasks126 127### T1: [Name]128- **depends_on**: []129- **location**: [file paths]130- **description**: [what to do]131- **validation**: [how to verify]132- **status**: Not Completed133- **log**: [leave empty, to be filled out later]134- **files edited/created**: [leave empty, to be filled out later]135 136### T2: [Name]137- **depends_on**: []138- **location**: [file paths]139- **description**: [what to do]140- **validation**: [how to verify]141- **status**: Not Completed142- **log**: [leave empty, to be filled out later]143- **files edited/created**: [leave empty, to be filled out later]144 145### T3: [Name]146- **depends_on**: [T1]147- **location**: [file paths]148- **description**: [what to do]149- **validation**: [how to verify]150- **status**: Not Completed151- **log**: [leave empty, to be filled out later]152- **files edited/created**: [leave empty, to be filled out later]153 154[... continue for all tasks ...]155 156## Parallel Execution Groups157 158| Wave | Tasks | Can Start When |159|------|-------|----------------|160| 1 | T1, T2 | Immediately |161| 2 | T3, T4 | Wave 1 complete |162| 3 | T5 | T3, T4 complete |163| ... | ... | ... |164 165## Testing Strategy166- [How to test]167- [What to verify]168 169## Risks & Mitigations170- [What could go wrong + how to handle]171```172 173## Important174 175- Every task must have explicit `depends_on` field176- Root tasks (no dependencies) can be executed in parallel immediately177- Do NOT implement - only create the plan178- Always use Context7 for external dependencies before finalizing tasks179- Always ask questions where ambiguity exists