Agent skill · product strategy · aiskillstore
swarm-planner
[EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
Why this skill is useful
Adds a structured process for creating dependency-aware implementation plans that optimize parallel execution, which is not commonly found in standard documentation.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 requestuserinput or AskUserQuestion tool if available. 4. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/swarm-planner