
Super Swarm Spark
Only to be triggered by explicit super-swarm-spark commands.
Install
npx skills add am-will/codex-skills --skill super-swarm-spark -g -a claude-code -y- Repository
- am-will/codex-skills1k
- Category
- Engineering
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Mediumabout 1,750 tokens
- Runs scripts
- No, instructions only
What it does
Only to be triggered by explicit super-swarm-spark commands.
Parallel Task Executor (Sparky Rolling 12-Agent Pool)
You are an Orchestrator for subagents. Parse plan files and delegate tasks in parallel using a rolling pool of up to 15 concurrent Sparky subagents. Keep launching new work whenever a slot opens until the plan is fully complete.
Primary orchestration goals:
- Keep the project moving continuously
- Ignore dependency maps
- Keep up to 15 agents running whenever pending work exists
- Give every subagent maximum path/file context
- Prevent filename/folder-name drift across parallel tasks
- Check every subagent result
- Ensure the plan file is updated as tasks complete
- Perform final integration fixes after all task execution
- Add/adjust tests, then run tests and fix failures
Process
Step 1: Parse Request
Extract from user request:
- Plan file: The markdown plan to read
- Task subset (optional): Specific task IDs to run
If no subset provided, run the full plan.
Step 2: Read & Parse Plan
- Find task subsections (e.g.,
### T1:or### Task 1.1:) - For each task, extract:
- Task ID and name
- Task linkage metadata for context only
- Full content (description, location, acceptance criteria, validation)
- Build task list
- If a task subset was requested, filter to only those IDs.
Step 3: Build Context Pack Per Task
Before launching a task, prepare a context pack that includes:
- Canonical file paths and folder paths the task must touch
- Planned new filenames (exact names, not suggestions)
- Neighboring tasks that touch the same files/folders
- Naming constraints and conventions from the plan/repo
- Any known cross-task expectations that could cause conflicts
Rules:
- Do not allow subagents to invent alternate file names for the same intent.
- Require explicit file targets in every subagent assignment.
- If a subagent needs a new file not in its context pack, it must report this before creating it.
