swarm-planner
Build Parallel-Ready Implementation Plans
Complex implementations often hide dependencies and block parallel work. This skill researches the codebase and produces validated, dependency-aware plans for coordinated agent execution.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "swarm-planner" from https://skillstore.io/skills/am-will-swarm-planner.md and its manifest at https://skillstore.io/api/skills/am-will-swarm-planner/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "swarm-planner". Plan passwordless authentication for the existing web application.
Expected outcome:
The plan starts with architecture and provider decisions, then separates schema, service, interface, and test tasks into dependency-based execution waves.
Using "swarm-planner". Plan an upgrade of the application framework without interrupting active feature work.
Expected outcome:
The result identifies compatibility research, package updates, migration work, regression testing, and rollout checks with explicit prerequisites and parallel opportunities.
Using "swarm-planner". Plan a reporting feature that requires new data aggregation and a dashboard.
Expected outcome:
The plan coordinates data contracts, aggregation logic, API work, dashboard development, and integration tests while marking which tasks can begin together.
Security Audit
SafeAll 11 static findings are false positives caused by Markdown inline-code markers and fenced examples in SKILL.md. The file contains planning instructions, templates, and placeholders; it does not contain Ruby or shell execution. No prompt injection or other intent-level security issue was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/am-will-swarm-planner/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/am-will-swarm-planner?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/am-will-swarm-planner?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/am-will-swarm-planner/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/am-will-swarm-planner.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
am-will. (2026). swarm-planner security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/am-will-swarm-planner/audits/5BibTeX citation
@techreport{am-will-am-will-swarm-planner-2026,
author = {am-will},
title = {swarm-planner security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/am-will-swarm-planner/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "swarm-planner security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "am-will"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/am-will-swarm-planner/audits/5"
identifiers:
- type: other
value: "skillstore:am-will-swarm-planner:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a Service Migration
Map schema, repository, service, endpoint, and test changes into ordered tasks with clear parallel work.
Coordinate a Product Feature
Separate frontend, backend, data, and validation work while preserving dependencies across teams.
Prepare an Agent Work Queue
Convert a complex repository change into atomic tasks that multiple coding agents can execute.
Try These Prompts
Use swarm-planner to plan adding [feature] to this repository. Ask about unclear requirements before creating the dependency-aware plan.
Plan [change] across the interface, service, data, and test layers. Identify task dependencies, file locations, validation criteria, and parallel execution groups.
Create a migration plan from [current framework or version] to [target]. Research current documentation, identify risks, and order compatibility, migration, and testing tasks.
Build a swarm-ready plan for [objective] under [constraints]. Inspect existing patterns, resolve ambiguity, define atomic tasks, map dependencies, group parallel waves, and request subagent review.
Best Practices
- Provide the objective, constraints, priorities, and acceptance criteria before planning begins.
- Answer clarification questions with concrete repository and product context.
- Review dependency links and validation criteria before assigning tasks to agents.
Avoid
- Do not use the skill when implementation should begin immediately without a planning phase.
- Do not omit known constraints and expect the planner to infer business priorities.
- Do not assign dependent tasks in parallel before their prerequisites are complete.