en un clic
swarm-planner
// [EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
// [EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution.
Use when the user wants an end-to-end premium visual design workflow for any type of website or web page created directly from images.
Create or update Codex hooks for global or project scope by asking for scope and hook type when ambiguous, then writing the hook config, scripts, and any required feature flag config.
Add a Codex plugin from a GitHub repo to a repo or personal marketplace using the current Codex plugin layout and marketplace metadata.
Create and update Codex custom agents using standalone custom-agent TOML files.
Only to be triggered by explicit /parallel-task commands.
Only to be triggered by explicit super-swarm-spark commands.
| name | swarm-planner |
| description | [EXPLICIT INVOCATION ONLY] Creates dependency-aware implementation plans optimized for parallel multi-agent execution. |
| metadata | {"invocation":"explicit-only"} |
Create implementation plans with explicit task dependencies optimized for parallel agent execution. This skill can be ran inside or outside of Plan Mode.
Codebase investigation:
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.
When anything is unclear or could reasonably be done multiple ways:
Structure the plan with explicit task dependencies using this format:
Each task MUST include:
T1, T2.1)[] for root tasks)Example:
T1: [depends_on: []] Create database schema migration
T2: [depends_on: []] Install required packages
T3: [depends_on: [T1]] Create repository layer
T4: [depends_on: [T1]] Create service interfaces
T5: [depends_on: [T3, T4]] Implement business logic
T6: [depends_on: [T2, T5]] Add API endpoints
T7: [depends_on: [T6]] Write integration tests
Tasks with empty/satisfied dependencies can run in parallel (T1, T2 above).
Save to <topic>-plan.md in the CWD.
After saving, spawn a subagent to review the plan:
Review this implementation plan for:
1. Missing dependencies between tasks
2. Ordering issues that would cause failures
3. Missing error handling or edge cases
4. Gaps, holes, gotchas.
Provide specific, actionable feedback. Do not ask questions.
Plan location: [file path]
Context: [brief context about the task]
If the subagent provides actionable feedback, revise the plan before yielding.
# Plan: [Task Name]
**Generated**: [Date]
## Overview
[Summary of task and approach]
## Prerequisites
- [Tools, libraries, access needed]
## Dependency Graph
[Visual representation of task dependencies] T1 ──┬── T3 ──┐ │ ├── T5 ── T6 ── T7 T2 ──┴── T4 ──┘
## Tasks
### T1: [Name]
- **depends_on**: []
- **location**: [file paths]
- **description**: [what to do]
- **validation**: [how to verify]
- **status**: Not Completed
- **log**: [leave empty, to be filled out later]
- **files edited/created**: [leave empty, to be filled out later]
### T2: [Name]
- **depends_on**: []
- **location**: [file paths]
- **description**: [what to do]
- **validation**: [how to verify]
- **status**: Not Completed
- **log**: [leave empty, to be filled out later]
- **files edited/created**: [leave empty, to be filled out later]
### T3: [Name]
- **depends_on**: [T1]
- **location**: [file paths]
- **description**: [what to do]
- **validation**: [how to verify]
- **status**: Not Completed
- **log**: [leave empty, to be filled out later]
- **files edited/created**: [leave empty, to be filled out later]
[... continue for all tasks ...]
## Parallel Execution Groups
| Wave | Tasks | Can Start When |
|------|-------|----------------|
| 1 | T1, T2 | Immediately |
| 2 | T3, T4 | Wave 1 complete |
| 3 | T5 | T3, T4 complete |
| ... | ... | ... |
## Testing Strategy
- [How to test]
- [What to verify]
## Risks & Mitigations
- [What could go wrong + how to handle]
depends_on field