Loading...
Loading...
Found 11 Skills
Only to be triggered by explicit /parallel-task commands.
Only to be triggered by explicit super-swarm-spark commands.
Only to be triggered by explicit /parallel-task-spark commands.
Analyze a task, pick the right fleet type, and generate a ready-to-launch fleet (fleet.json + prompt.md files). Discovers available fleet skills dynamically. Use when the user wants to run work in parallel, asks to "plan a fleet", or says "fleet-plan".
Only to be triggered by explicit super-swarm commands.
Launch multiple sub-agents in parallel to execute tasks across files or targets with intelligent model selection, quality-focused prompting, and meta-judge → LLM-as-a-judge verification
Spawn isolated agents for parallel task execution. Local mode auto-selects Codex sub-agents or Claude teams. Distributed mode uses tmux + Agent Mail (process isolation, persistence). Triggers: "swarm", "spawn agents", "parallel work".
Use when an approved current phase has 3 or more independent ready tasks and parallel execution will materially reduce cycle time. Orchestrates bounded workers, monitors blockers and file conflicts, coordinates rescues, and hands off to planning or reviewing when the current execution scope is complete. Use for prompts about swarming, parallel workers, launching multiple agents, coordinating a worker pool, or running approved current-phase work at scale.
Orchestrate parallel implementation with coder/overseer pairs. Coders implement decomposed tasks using evanflow-tdd; overseers review each coder's output for bugs, gaps, errors, AND cohesion violations against a shared contract. A final integration overseer checks cross-coder cohesion. Use for plans with 3+ truly independent tasks that share an interface contract.
Spawn claude, codex, or gemini CLI workers in tmux panes for parallel task execution
Use when the user says "vm", "voice mode", "team", "coordinate", or needs to orchestrate multiple agents working on related tasks in parallel