bmad-epic-worktree

Automate sequential delivery of Epic user stories via isolated Git worktrees.

40|6|Updated Feb 16, 2026

Search Tags:#automation #git #worktree #agile #epic #sequential delivery

Ready to run

npx skills add https://github.com/terryso/claude-bmad-skills --skill bmad-epic-worktree

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-epic-worktree
Source: https://github.com/terryso/claude-bmad-skills/tree/main/.claude/skills/bmad-epic-worktree
Command: npx skills add https://github.com/terryso/claude-bmad-skills --skill bmad-epic-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the sequential delivery of all user stories within an Epic, ensuring each story is developed, tested, and merged in an isolated environment before proceeding to the next.

Core Features & Use Cases

Epic-level Automation: Manages the end-to-end delivery of multiple user stories belonging to a single Epic.
Isolated Development: Each story is processed in its own Git worktree, preventing interference between stories.
Sequential Execution: Guarantees that one story must complete successfully before the next one begins.
Use Case: Automate the development and integration of an entire Epic, from initial story creation to final status updates, with high confidence due to isolated testing and merging.

Quick Start

Execute the bmad epic worktree skill for epic number 3.

Frequently Asked Questions about bmad-epic-worktree

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

FAQPage Schema

How do I automate sequential delivery of user stories within an Agile epic?▼

Sequential delivery of an Agile epic is automated by orchestrating story execution in isolated Git worktrees, ensuring each story is developed, tested, and merged before the next begins.

What is the benefit of using isolated Git worktrees for epic development?▼

Isolated Git worktrees prevent interference between stories during epic development by providing each story its own dedicated branch environment, ensuring tested changes merge cleanly without conflicts.

How does epic automation handle failing tests or unresolved issues during story delivery?▼

Epic automation halts sequential delivery when tests fail or issues remain unresolved, ensuring that subsequent stories are only processed after the current story passes all tests and merges successfully.

Can I automatically select an epic for sequential delivery without specifying a number?▼

Yes, you can automatically select an epic for sequential delivery without an argument, as the automation auto-selects the smallest incomplete epic available in the repository.

What happens after a story completes in the sequential epic delivery workflow?▼

After a story completes in the sequential epic delivery workflow, its isolated worktree changes are merged and the story status is updated before the automation proceeds to trigger the next story.

When should I use automated sequential epic delivery instead of parallel story development?▼

Automated sequential epic delivery is ideal when stories have dependencies requiring strict order, whereas parallel story development suits independent stories needing simultaneous isolated worktree branching.