bmad-story-worktree

Automate BMAD user story delivery in an isolated Git worktree.

40|6|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/terryso/claude-bmad-skills --skill bmad-story-worktree
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-story-worktree
Source: https://github.com/terryso/claude-bmad-skills/tree/main/.claude/skills/bmad-story-worktree
Command: npx skills add https://github.com/terryso/claude-bmad-skills --skill bmad-story-worktree

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the entire user story delivery pipeline within an isolated Git worktree, ensuring code quality and stability before merging.

Core Features & Use Cases

  • Isolated Development: Creates a separate worktree for each story, preventing conflicts with the main codebase.
  • End-to-End Automation: Manages the full lifecycle from story creation, development, testing, code review, auto-fixing, to merging and status updates.
  • Safety Assurance: Guarantees that code is merged only after passing all automated tests and code reviews, significantly reducing integration risks.
  • Use Case: A developer can initiate this skill for a specific story number, and it will handle all the necessary steps, including setting up a clean environment, writing code, running tests, and performing a safe merge, all without manual intervention until a critical failure.

Quick Start

Execute the bmad-story-worktree skill with the story number 1.1 to begin the delivery process.

Frequently Asked Questions about bmad-story-worktree

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

FAQPage Schema
How do I automate user story delivery in an isolated Git worktree?

Automated user story delivery in an isolated Git worktree handles the complete pipeline from story creation through development, QA testing, code review, auto-fixing issues, and conditional merging to ensure code stability.

What is the best way to prevent integration conflicts during feature development?

Using Git worktree for isolated development prevents integration conflicts by creating a separate working directory for each story, keeping the main codebase stable until automated tests pass and safe merging occurs.

How does automated code review and auto-fixing work before merging a story?

Automated code review scans for HIGH and MEDIUM issues during story delivery, automatically fixing them before merging. If critical issues remain unresolved, the process halts merging and preserves the worktree for manual intervention.

Can I use conditional merging to ensure code quality in CI/CD pipelines?

Conditional merging ensures CI/CD code quality by only merging story branches after all automated tests pass and code reviews clear. If conditions fail, the worktree is preserved for manual fixes rather than auto-merging broken code.

What happens to my Git worktree if automated testing fails during story delivery?

If automated testing fails during story delivery, the Git worktree is preserved rather than discarded. This allows developers to manually intervene, inspect failures, and fix issues before attempting another conditional merge.

Do I need to manually set up a Git worktree before starting story development?

No manual Git worktree setup is needed. The automated story delivery pipeline creates the isolated worktree environment automatically when initiated with a specific story number, handling the full lifecycle setup without developer intervention.