parallel-task-spark
Execute Development Plans in Parallel
Large development plans are slow when independent tasks run sequentially. This skill schedules ready tasks in parallel, validates results, commits changes, and updates plan logs.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "parallel-task-spark" from https://skillstore.io/skills/am-will-parallel-task-spark.md and its manifest at https://skillstore.io/api/skills/am-will-parallel-task-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 "parallel-task-spark". Run the complete user profile plan.
Expected outcome:
- Assigned three ready tasks in the first wave and two dependent tasks in the second wave.
- Validated each task with test evidence and local commits.
- Updated the plan with completion logs, modified files, and remaining issues.
Using "parallel-task-spark". Run tasks T3 and T7 from the authentication plan.
Expected outcome:
Included required dependencies, completed available tasks in waves, recorded verification evidence, and reported one blocked task with its next step.
Security Audit
SafeAll 13 external-command findings are false positives caused by Markdown inline code and fenced examples; SKILL.md contains no Ruby or shell execution syntax. The reconnaissance alert also misclassifies an agent-role requirement, and no semantic threat 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-parallel-task-spark/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/am-will-parallel-task-spark?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/am-will-parallel-task-spark?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/am-will-parallel-task-spark/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/am-will-parallel-task-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). parallel-task-spark security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/am-will-parallel-task-spark/audits/5BibTeX citation
@techreport{am-will-am-will-parallel-task-spark-2026,
author = {am-will},
title = {parallel-task-spark security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/am-will-parallel-task-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: "parallel-task-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-parallel-task-spark/audits/5"
identifiers:
- type: other
value: "skillstore:am-will-parallel-task-spark:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Parallel Feature Delivery
Run independent implementation tasks together while preserving dependency order and task-level validation.
Coordinated Refactoring
Divide a refactoring plan into safe waves with focused commits and recorded outcomes.
Test-Guided Implementation
Require failing tests before implementation and passing evidence before each task is complete.
Try These Prompts
Run /parallel-task-spark plans/profile-plan.md and complete every task in dependency order.
Run /parallel-task-spark plans/auth-plan.md for tasks T1, T2, and T4, including their required dependencies.
Execute /parallel-task-spark plans/migration-plan.md and require RED-to-GREEN evidence or a documented alternative for every task.
Execute /parallel-task-spark plans/release-plan.md in dependency waves, confirm local commits, update each task log, and report unresolved issues.
Best Practices
- Use stable, unique task identifiers and explicit dependency lists in every plan.
- Include acceptance criteria and exact validation commands for each task.
- Review local commits and plan logs before starting the next wave.
Avoid
- Do not invoke the skill on an unstructured document without clear task sections.
- Do not assign overlapping files to parallel tasks without coordination.
- Do not expect remote pushes; the workflow creates local commits only.