run-stories

Name: run-stories
Availability: InStock
Author: kelsi-andrewss

Execute multiple stories in parallel with dependency-aware scheduling and isolated git worktrees.

1|Updated Feb 21, 2026

Search Tags:#automation #orchestration #parallel-execution #dependency-management #git-worktree #story-management #run-stories

Ready to run

npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill run-stories

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: run-stories
Source: https://github.com/kelsi-andrewss/claude-multi-agent-pipeline/tree/main/skills/run-stories
Command: npx skills add https://github.com/kelsi-andrewss/claude-multi-agent-pipeline --skill run-stories

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating and executing multiple stories across epics in parallel while respecting dependencies, preventing write conflicts, and tracking progress across isolated worktrees.

Core Features & Use Cases

Parallel execution of ready/draft stories with per-story isolation via git worktrees.
Dependency-aware scheduling, bootstrap serialization, and conflict-aware batching.
Cross-epic coordination and per-story state management with plan and progress reporting across teams.

Quick Start

Start by issuing the /run-stories command with optional story-NNN or epic-NNN tokens to trigger parallel execution.

Frequently Asked Questions about run-stories

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

FAQPage Schema

How do I run multiple stories in parallel without write conflicts?▼

Parallel story execution prevents write conflicts by isolating each story in a separate git worktree, building an execution plan that schedules tasks based on dependency-aware batching.

What is dependency-aware scheduling for parallel story execution?▼

Dependency-aware scheduling orchestrates parallel story execution by respecting inter-story dependencies, serializing bootstrap processes, and managing per-story state across isolated worktrees.

How do I coordinate story execution across multiple epics?▼

Cross-epic coordination manages parallel story execution by loading plan data, assigning agents to isolated worktrees, tracking progress, and reporting structured final results.

Can I use git worktrees to isolate parallel story execution?▼

Yes, git worktrees provide per-story isolation for parallel execution, preventing file conflicts while the orchestration layer tracks progress and manages state across epics.

How do I start parallel execution for specific stories or epics?▼

Trigger parallel execution by issuing the run-stories command with optional story-NNN or epic-NNN tokens to build the execution plan and assign agents.

What happens when bootstrap processes conflict during parallel story execution?▼

Bootstrap serialization handles conflicts during parallel story execution by sequencing bootstrap steps within the execution plan, ensuring isolated worktrees maintain per-story state integrity.