[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.

Swarm Ready Planner Create implementation plans with explicit task dependencies optimized for parallel agent execution. This skill can be ran inside or outside of Plan Mode. Core Principles 1. Explore Codebase : Investigate architecture, patterns, existing implementations, dependencies, and frameworks in use. 2. Fresh Documentation First : Use Context7 for ANY external library, framework, or API before planning tasks 3. Ask Questions : Clarify ambiguities and seek clarification on scope, constraints, or priorities throughout the planning process. At any time. 4. Explicit Dependencies : Every task declares what it depends on, enabling maximum parallelization 5. Atomic Tasks : Each task is independently executable by a single agent 6. Review Before Yield : A subagent reviews the plan for gaps before finalizing Process 1. Research Codebase investigation: Architecture, patterns, existing implementations Dependencies and frameworks in use 1a. Optional: Stop to Clarification Questions 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. If architecture is present, skip 1a and move onto next step. 2. Documentation Documentation retrieval (REQUIRED for external dependencies): Use 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. This ensures version accurate APIs, correct parameters, and current best practices. 3. STOP and Request User Input When anything is unclear or could reasonably be done multiple ways: Stop and ask clarifying questions immediately Do not make assumptions about scope, constraints, or priorities Questions should reduce risk and eliminate ambiguity Always offer recommendations for clarification questions. Use request user input or AskUserQuestion tool if available. 4. Create Dependency Aware Plan Structure the plan with explicit task dependencies using this format: Task Dependency Format Each task MUST include: id : Unique identifier (e.g., T1 , T2.1 ) depends on : Array of task IDs that must complete first (empty [] for root tasks) description : What the task accomplishes location : File paths involved validation : acceptance criteria Example: Tasks with empty/satisfied dependencies can run in parallel (T1, T2 above). 4. Save Plan Save to <topic plan.md in the CWD. 5. Subagent Review After saving, spawn a subagent to review the plan: If the subagent provides actionable feedback, revise the plan before yielding. Plan Template [Visual representation of task dependencies] T1 ──┬── T3 ──┐ │ ├── T5 ── T6 ── T7 T2 ──┴── T4 ──┘ Important Every task must have explicit depends on field Root tasks (no dependencies) can be executed in parallel immediately Do NOT implement only create the plan Always use Context7 for external dependencies before finalizing tasks Always ask questions where ambiguity exists

swarm-planner