swarm-execute

Orchestrate parallel execution of prd.json user stories in isolated worktrees.

5|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/adelrioj/claude-skills --skill swarm-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swarm-execute
Source: https://github.com/adelrioj/claude-skills/tree/main/skills/swarm-execute
Command: npx skills add https://github.com/adelrioj/claude-skills --skill swarm-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate parallel execution of prd.json user stories by creating isolated worktrees for each story, spawning teammates, and enforcing dependencies and quality gates so large plans deliver quickly without conflicting changes.

Core Features & Use Cases

  • Spawns dedicated teammates per story in isolated worktrees to execute stories concurrently.
  • Monitors progress, handles prerequisites, merges results, and enforces per-story quality gates.
  • Supports branching, progress reporting, and findings aggregation for batch reviews.

Quick Start

Initiate a swarm by triggering the swarm-execute flow once tasks/prd.json is prepared; the system will plan batches, spawn teammates in isolated worktrees, and enforce quality gates.

Frequently Asked Questions about swarm-execute

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute user stories from prd.json in parallel using Claude Code?

You can execute prd.json stories in parallel by spawning Claude Code teammates in isolated worktrees, which concurrently processes stories while enforcing dependency order and quality gates to prevent conflicting changes.

What is parallel agent orchestration and how does it handle dependencies?

Parallel agent orchestration spawns dedicated teammates per story in isolated worktrees, enforcing dependency order and per-story quality gates so large plans deliver quickly without conflicting changes.

How do I start a swarm execution flow for my project tasks?

To start swarm execution, prepare your tasks/prd.json file with user stories, then trigger the swarm-execute flow; the system plans batches, spawns teammates in isolated worktrees, and enforces quality gates automatically.

Can I use isolated worktrees to run concurrent agent teams without merge conflicts?

Yes, spawning teammates in isolated worktrees allows each agent to execute stories concurrently without merge conflicts, while the orchestration system handles prerequisites and merges results safely.

What's the best way to review progress and findings from parallel story execution?

The swarm execution system captures progress, findings, and merge readiness across all spawned teammates, aggregating results to support batch reviews and risk-managed story execution.

When should I avoid parallel story execution with agent teams?

Avoid parallel story execution when user stories have complex interdependencies that cannot be resolved by enforcing dependency order, or when isolated worktrees cannot sufficiently isolate conflicting changes.