bmad-codex

Name: bmad-codex
Availability: InStock
Author: jongensutrecht

Coordinate BMAD Codex story workflows with isolated worktrees and proof-gated merges.

1|Updated Jan 13, 2026

Search Tags:#worktrees #governance #merge workflow #bmad #repository automation #proof gate #cto rules

Ready to run

npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill bmad-codex

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bmad-codex
Source: https://github.com/jongensutrecht/demo-ai-stack/tree/main/.claude/skills/bmad-codex
Command: npx skills add https://github.com/jongensutrecht/demo-ai-stack --skill bmad-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill gives you a repeatable way to implement repository stories in isolated worktrees while keeping governance, verification, and merge control aligned.

Core Features & Use Cases

Per-story worktree and branch setup for BMAD Codex execution.
Mandatory review of repository governance sources before implementation begins.
Proof-gated merges with final.json evidence, quality gates, and handoff support when context changes.
Use it when you need a safe, traceable path from plan to merge in a complex repository.

Quick Start

Ask the skill to start a BMAD Codex story workflow for the target repository and keep all changes in the approved worktree process.

Frequently Asked Questions about bmad-codex

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

FAQPage Schema

How do I enforce governance checks during a repository merge workflow?▼

To enforce governance checks during a repository merge workflow, you can use this Skill to mandate repository governance file reviews and execute primary quality gates before any story integration occurs.

What is a proof-gated merge workflow for story-driven development?▼

A proof-gated merge workflow for story-driven development is a controlled integration process that requires final.json evidence artifacts and passing primary quality gate execution before isolated worktree branches merge into the repository.

How do I set up isolated worktrees for per-story branch development?▼

You can set up isolated worktrees for per-story branch development by initiating the BMAD Codex story workflow, which configures branch isolation and enforces strict file-size and function-count limits for each repository story.

Does this workflow support handoff when context changes during story implementation?▼

Yes, the workflow supports handoff when context changes during story implementation by maintaining final.json proof artifacts and traceable governance records, allowing controlled integration or transfer of the isolated worktree state.

What are the limitations of using isolated worktrees for repository story delivery?▼

Limitations of using isolated worktrees for repository story delivery include strict file-size and function-count limits enforced during execution, requiring all changes to pass primary quality gates and generate final.json proof artifacts before merging.