swarm-planner

Name: swarm-planner
Author: am-will

222stars12forks

How to install swarm-planner?

am-will/swarms/swarm-planner

$npx -y skills add am-will/swarms --skill swarm-planner

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Swarm-Ready Planner
2
3	Create implementation plans with explicit task dependencies optimized for parallel agent execution. This skill can be ran inside or outside of Plan Mode.
4
5	## Core Principles
6
7	1. Explore Codebase: Investigate architecture, patterns, existing implementations, dependencies, and frameworks in use.
8	2. Fresh Documentation First: Use Context7 for ANY external library, framework, or API before planning tasks
9	3. Ask Questions: Clarify ambiguities and seek clarification on scope, constraints, or priorities throughout the planning process. At any time.
10	4. Explicit Dependencies: Every task declares what it depends on, enabling maximum parallelization
11	5. Atomic Tasks: Each task is independently executable by a single agent
12	6. Review Before Yield: A subagent reviews the plan for gaps before finalizing
13
14	## Process
15
16	### 1. Research
17
18	Codebase investigation:
19	- Architecture, patterns, existing implementations
20	- Dependencies and frameworks in use
21
22	### 1a. Optional: Stop to Clarification Questions
23
24	- 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.
25	- If architecture is present, skip 1a and move onto next step.
26
27	### 2. Documentation
28
29	Documentation retrieval (REQUIRED for external dependencies):
30
31	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.
32
33	This ensures version-accurate APIs, correct parameters, and current best practices.
34
35	### 3. STOP and Request User Input
36
37	When anything is unclear or could reasonably be done multiple ways:
38	- Stop and ask clarifying questions immediately
39	- Do not make assumptions about scope, constraints, or priorities
40	- Questions should reduce risk and eliminate ambiguity
41	- Always offer recommendations for clarification questions.
42	- Use request_user_input or AskUserQuestion tool if available.
43
44	### 4. Create Dependency-Aware Plan
45
46	Structure the plan with explicit task dependencies using this format:
47
48	#### Task Dependency Format
49
50	Each task MUST include:
51	- id: Unique identifier (e.g., `T1`, `T2.1`)
52	- depends_on: Array of task IDs that must complete first (empty `[]` for root tasks)
53	- description: What the task accomplishes
54	- location: File paths involved
55	- validation: acceptance criteria
56
57	Example:
58	```
59	T1: [depends_on: []] Create database schema migration
60	T2: [depends_on: []] Install required packages
61	T3: [depends_on: [T1]] Create repository layer
62	T4: [depends_on: [T1]] Create service interfaces
63	T5: [depends_on: [T3, T4]] Implement business logic
64	T6: [depends_on: [T2, T5]] Add API endpoints
65	T7: [depends_on: [T6]] Write integration tests
66	```
67
68	Tasks with empty/satisfied dependencies can run in parallel (T1, T2 above).
69
70	### 4. Save Plan
71
72	Save to `<topic>-plan.md` in the CWD.
73
74	### 5. Subagent Review
75
76	After saving, spawn a subagent to review the plan:
77
78	```
79	Review this implementation plan for:
80	1. Missing dependencies between tasks
81	2. Ordering issues that would cause failures
82	3. Missing error handling or edge cases
83	4. Gaps, holes, gotchas.
84
85	Provide specific, actionable feedback. Do not ask questions.
86
87	Plan location: [file path]
88	Context: [brief context about the task]
89	```
90
91	If the subagent provides actionable feedback, revise the plan before yielding.
92
93
94	## Plan Template
95
96	```markdown
97	# Plan: [Task Name]
98
99	Generated: [Date]
100
101	## Overview
102	[Summary of task and approach]
103
104	## Prerequisites
105	- [Tools, libraries, access needed]
106
107	## Dependency Graph
108
109	```
110	[Visual representation of task dependencies]
111	T1 ──┬── T3 ──┐
112	│ ├── T5 ── T6 ── T7
113	T2 ──┴── T4 ──┘
114	```
115
116	## Tasks
117
118	### T1: [Name]
119	- depends_on: []
120	- location: [file paths]
121	- description: [what to do]
122	- validation: [how to verify]
123	- status: Not Completed
124	- log: [leave empty, to be filled out later]
125	- files edited/created: [leave empty, to be filled out later]
126
127	### T2: [Name]
128	- depends_on: []
129	- location: [file paths]
130	- description: [what to do]
131	- validation: [how to verify]
132	- status: Not Completed
133	- log: [leave empty, to be filled out later]
134	- files edited/created: [leave empty, to be filled out later]
135
136	### T3: [Name]
137	- depends_on: [T1]
138	- location: [file paths]
139	- description: [what to do]
140	- validation: [how to verify]
141	- status: Not Completed
142	- log: [leave empty, to be filled out later]
143	- files edited/created: [leave empty, to be filled out later]
144
145	[... continue for all tasks ...]
146
147	## Parallel Execution Groups
148
149	\| Wave \| Tasks \| Can Start When \|
150	\|------\|-------\|----------------\|
151	\| 1 \| T1, T2 \| Immediately \|
152	\| 2 \| T3, T4 \| Wave 1 complete \|
153	\| 3 \| T5 \| T3

People who liked this also viewed

6 picks

Type

paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026157k5
subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026154k259k
dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026143k259k
browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 202685k4.6k
wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 202675k182k
wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 202666k137

swarm-planner

222stars12forks

View on GitHub

How to install swarm-planner?

am-will/swarms/swarm-planner

$npx -y skills add am-will/swarms --skill swarm-planner

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	# Swarm-Ready Planner
2
3	Create implementation plans with explicit task dependencies optimized for parallel agent execution. This skill can be ran inside or outside of Plan Mode.
4
5	## Core Principles
6
7	1. Explore Codebase: Investigate architecture, patterns, existing implementations, dependencies, and frameworks in use.
8	2. Fresh Documentation First: Use Context7 for ANY external library, framework, or API before planning tasks
9	3. Ask Questions: Clarify ambiguities and seek clarification on scope, constraints, or priorities throughout the planning process. At any time.
10	4. Explicit Dependencies: Every task declares what it depends on, enabling maximum parallelization
11	5. Atomic Tasks: Each task is independently executable by a single agent
12	6. Review Before Yield: A subagent reviews the plan for gaps before finalizing
13
14	## Process
15
16	### 1. Research
17
18	Codebase investigation:
19	- Architecture, patterns, existing implementations
20	- Dependencies and frameworks in use
21
22	### 1a. Optional: Stop to Clarification Questions
23
24	- 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.
25	- If architecture is present, skip 1a and move onto next step.
26
27	### 2. Documentation
28
29	Documentation retrieval (REQUIRED for external dependencies):
30
31	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.
32
33	This ensures version-accurate APIs, correct parameters, and current best practices.
34
35	### 3. STOP and Request User Input
36
37	When anything is unclear or could reasonably be done multiple ways:
38	- Stop and ask clarifying questions immediately
39	- Do not make assumptions about scope, constraints, or priorities
40	- Questions should reduce risk and eliminate ambiguity
41	- Always offer recommendations for clarification questions.
42	- Use request_user_input or AskUserQuestion tool if available.
43
44	### 4. Create Dependency-Aware Plan
45
46	Structure the plan with explicit task dependencies using this format:
47
48	#### Task Dependency Format
49
50	Each task MUST include:
51	- id: Unique identifier (e.g., `T1`, `T2.1`)
52	- depends_on: Array of task IDs that must complete first (empty `[]` for root tasks)
53	- description: What the task accomplishes
54	- location: File paths involved
55	- validation: acceptance criteria
56
57	Example:
58	```
59	T1: [depends_on: []] Create database schema migration
60	T2: [depends_on: []] Install required packages
61	T3: [depends_on: [T1]] Create repository layer
62	T4: [depends_on: [T1]] Create service interfaces
63	T5: [depends_on: [T3, T4]] Implement business logic
64	T6: [depends_on: [T2, T5]] Add API endpoints
65	T7: [depends_on: [T6]] Write integration tests
66	```
67
68	Tasks with empty/satisfied dependencies can run in parallel (T1, T2 above).
69
70	### 4. Save Plan
71
72	Save to `<topic>-plan.md` in the CWD.
73
74	### 5. Subagent Review
75
76	After saving, spawn a subagent to review the plan:
77
78	```
79	Review this implementation plan for:
80	1. Missing dependencies between tasks
81	2. Ordering issues that would cause failures
82	3. Missing error handling or edge cases
83	4. Gaps, holes, gotchas.
84
85	Provide specific, actionable feedback. Do not ask questions.
86
87	Plan location: [file path]
88	Context: [brief context about the task]
89	```
90
91	If the subagent provides actionable feedback, revise the plan before yielding.
92
93
94	## Plan Template
95
96	```markdown
97	# Plan: [Task Name]
98
99	Generated: [Date]
100
101	## Overview
102	[Summary of task and approach]
103
104	## Prerequisites
105	- [Tools, libraries, access needed]
106
107	## Dependency Graph
108
109	```
110	[Visual representation of task dependencies]
111	T1 ──┬── T3 ──┐
112	│ ├── T5 ── T6 ── T7
113	T2 ──┴── T4 ──┘
114	```
115
116	## Tasks
117
118	### T1: [Name]
119	- depends_on: []
120	- location: [file paths]
121	- description: [what to do]
122	- validation: [how to verify]
123	- status: Not Completed
124	- log: [leave empty, to be filled out later]
125	- files edited/created: [leave empty, to be filled out later]
126
127	### T2: [Name]
128	- depends_on: []
129	- location: [file paths]
130	- description: [what to do]
131	- validation: [how to verify]
132	- status: Not Completed
133	- log: [leave empty, to be filled out later]
134	- files edited/created: [leave empty, to be filled out later]
135
136	### T3: [Name]
137	- depends_on: [T1]
138	- location: [file paths]
139	- description: [what to do]
140	- validation: [how to verify]
141	- status: Not Completed
142	- log: [leave empty, to be filled out later]
143	- files edited/created: [leave empty, to be filled out later]
144
145	[... continue for all tasks ...]
146
147	## Parallel Execution Groups
148
149	\| Wave \| Tasks \| Can Start When \|
150	\|------\|-------\|----------------\|
151	\| 1 \| T1, T2 \| Immediately \|
152	\| 2 \| T3, T4 \| Wave 1 complete \|
153	\| 3 \| T5 \| T3

People who liked this also viewed

6 picks

Type