bmad-bundle

Orchestrate proof-gated BMAD story bundles with enforced CTO review.

1|Updated Jan 13, 2026
One-click install
npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill bmad-bundle
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-bundle
Source: https://github.com/jongensutrecht/demo-ai-stack/tree/main/.claude/skills/bmad-bundle
Command: npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill bmad-bundle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a complex BMAD delivery run into a controlled, proof-gated workflow so story creation, execution, review, and merge safety happen in the right order without breaking repo governance.

Core Features & Use Cases

  • Main-merge worktree orchestration: Creates a dedicated integration worktree and keeps BMAD artifacts off the main branch.
  • Universal CTO guardrails: Forces full CTO review before execution and again before final merge, preserving in-scope, out-of-scope, UNKNOWN state, and prioritized risk reporting.
  • Proof-gated delivery: Uses run metadata and final proof files to decide whether a story can be marked done.
  • Use Case: Run this Skill when you need a repeatable, fail-closed process for implementing multiple stories in a governed repository with strict quality gates.

Quick Start

Use the bmad-bundle skill with the attached input markdown to generate a proof-gated BMAD run, enforce CTO review, and prepare the final merge path.

Frequently Asked Questions about bmad-bundle

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

FAQPage Schema
How do I enforce CTO review gates during a multi-story development workflow?

You can enforce CTO review gates by orchestrating a proof-gated workflow that mandates full Universal CTO Review v2.4 coverage before execution and again before final merge, ensuring in-scope, out-of-scope, and UNKNOWN states are preserved.

What is a proof-gated BMAD story bundle and how does it work?

A proof-gated BMAD story bundle is a controlled delivery run that uses run metadata and final proof files to decide whether a story can be marked done, applying deterministic gating and fail-closed handling for P1/P2 blockers.

How do I keep BMAD artifacts off the main branch when running multi-step implementations?

You can keep artifacts off the main branch by using main-merge worktree orchestration, which creates a dedicated integration worktree and per-story branches to isolate implementation artifacts until the final merge path is prepared.

Can I use proof-gated delivery for repository governance with strict quality checks?

Yes, you can apply proof-gated delivery to repo-governed development runs by enforcing deterministic gating, repo-native quality checks, and fail-closed handling of file limits and P1/P2 blockers across multi-step workflows.

What happens if a P1 or P2 blocker is detected during a governed repo development run?

If a P1 or P2 blocker is detected, the workflow applies fail-closed handling to halt progression, ensuring the story cannot be marked done until the blocker is resolved and passes the deterministic quality gates.

Does bmad-bundle require any specific dependencies to run repo-governed development workflows?

No specific dependencies are required to run these proof-gated BMAD workflows, but you need a governed repository environment that supports worktree creation, per-story branches, and repo-native quality checks to enforce the gates properly.