parallel-task-spark — Claude Code skill: what it does, how to install
An orchestration skill that runs markdown plan tasks in parallel waves using Sparky subagents with dependency checks. It helps when executing modular plans with strict TDD.
npx skills add am-will/codex-skills --skill parallel-task-spark -a claude-codeWhat parallel-task-spark does
This orchestrator parses a markdown roadmap, analyzes depends_on entries, and builds an execution graph. Work proceeds in parallel waves using child agents assigned to the sparky role. The workflow requires manual invocation via the /parallel-task-spark slash command and never triggers passively during conversation.
Workers follow a test-driven approach by default. They generate failing tests through a tdd_test_writer role before touching application code. When an item cannot undergo automated tests, the worker must document an explicit reason alongside alternative verification like static checks. Each agent stages and commits only its relevant files locally. Git push operations are strictly prohibited inside the subagent cycle to avoid polluting remote branches.
Strict plan formatting is mandatory because broken task identifiers or malformed dependency lists halt the parser immediately. However, committing each wave locally before starting the next prevents merge clashes when multiple agents touch the tree.
What it helps with
- split a markdown roadmap into dependency-ordered work waves
- dispatch unblocked tasks across parallel worker agents
- enforce red-green TDD steps before production edits
- commit file changes locally per agent without remote pushing
- update plan files with progress notes and completion status
Example prompts for the agent
- /parallel-task-spark docs/backend-plan.md
- /parallel-task-spark ./plans/checkout-plan.md TASK_1 TASK_3
- /parallel-task-spark architecture-plan.md --tasks T5 T8
How to install parallel-task-spark
1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill parallel-task-spark -a claude-code2Manually: put the files in place
~/.claude/skills/parallel-task-spark/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/parallel-task-spark/
1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill parallel-task-spark -a codex2Manually: put the files in place
.agents/skills/parallel-task-spark/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill parallel-task-spark -a cursor2Manually: put the files in place
.cursor/skills/parallel-task-spark/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install am-will/codex-skills parallel-task-spark2Manually: put the files in place
.github/skills/parallel-task-spark/SKILL.md1Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill parallel-task-spark -a gemini-cli2Platform CLI
gemini skills install https://github.com/am-will/codex-skills --path skills/parallel-task-sparkManually: put the files in place
.devin/skills/parallel-task-spark/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add am-will/codex-skills --skill parallel-task-spark -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about parallel-task-spark
How to install parallel-task-spark in Claude Code?
Run npx skills add am-will/codex-skills --skill parallel-task-spark -a claude-code in your terminal. The skill file will be placed at ~/.claude/skills/parallel-task-spark/SKILL.md.
What does parallel-task-spark do?
It parses a markdown plan file, determines task readiness via dependency markers, and spins up parallel sparky subagents. Each agent verifies its work through tests, commits changes locally, and appends completion notes to the plan document.
Can worker subagents push commits to a remote git branch?
No, subagents are strictly restricted from running git push. They must only stage their assigned files and make a local commit to prevent merge conflicts during concurrent runs.