super-swarm-spark
Execute Development Plans with Parallel Subagents
Large development plans are slow and difficult to coordinate across concurrent tasks. This skill schedules Sparky subagents, validates results, integrates changes, and updates the source plan.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "super-swarm-spark" from https://skillstore.io/skills/am-will-super-swarm-spark.md and its manifest at https://skillstore.io/api/skills/am-will-super-swarm-spark/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 "super-swarm-spark". Execute all tasks in plans/user-profile-plan.md.
Expected outcome:
- Completed six assigned tasks with a maximum of six active workers.
- Resolved one shared-file conflict during integration.
- Added profile validation coverage and completed the required test run.
- Updated the plan with task logs and modified file paths.
Using "super-swarm-spark". Run tasks T3 and T7 from plans/auth-plan.md.
Expected outcome:
- Completed T3 and T7 while leaving all other tasks unchanged.
- Validated both task acceptance criteria and recorded their local commits.
- Reported one deferred integration test with its blocking dependency.
Security Audit
SafeAll 11 static findings are false positives caused by Markdown backticks, code fences, and inline role labels in SKILL.md. The file contains orchestration instructions but no Ruby execution, shell commands, system reconnaissance, or auditor-directed prompt injection.
Risk Factors
⚙️ External commands (10)
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-super-swarm-spark/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/am-will-super-swarm-spark?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/am-will-super-swarm-spark?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/am-will-super-swarm-spark/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/am-will-super-swarm-spark.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). super-swarm-spark security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/am-will-super-swarm-spark/audits/5BibTeX citation
@techreport{am-will-am-will-super-swarm-spark-2026,
author = {am-will},
title = {super-swarm-spark security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/am-will-super-swarm-spark/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: "super-swarm-spark 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-super-swarm-spark/audits/5"
identifiers:
- type: other
value: "skillstore:am-will-super-swarm-spark:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Deliver a Feature Plan
Execute a complete feature plan in parallel, validate each task, and integrate the resulting changes.
Complete Selected Maintenance Tasks
Run only chosen task identifiers from a larger maintenance plan while preserving shared naming and path constraints.
Coordinate Test and Integration Work
Distribute implementation tasks, resolve cross-task conflicts, and run a final regression pass before completion.
Try These Prompts
/super-swarm-spark plans/release-plan.md. Execute every task, validate each result, update the plan, and provide the execution summary.
/super-swarm-spark plans/auth-plan.md T1 T2 T4. Run only these tasks, preserve canonical paths, and report deferred validation.
/super-swarm-spark plans/api-plan.md. Highlight tasks sharing files, enforce the plan's canonical names, and reconcile conflicts during integration.
/super-swarm-spark plans/migration-plan.md --tasks T3 T5 T7. Complete the subset, add regression tests, rerun failures, and document blockers with evidence.
Best Practices
- Use plans with explicit task identifiers, canonical file paths, acceptance criteria, and validation steps.
- Choose task subsets that can proceed independently when the plan contains strict dependencies.
- Review local commits, plan updates, and final test results before sharing the branch.
Avoid
- Do not launch a vague plan that omits file ownership or expected outputs.
- Do not parallelize tightly ordered migrations or tasks with unresolved prerequisites.
- Do not allow multiple tasks to invent different names for the same file or feature.