WEBELEON // TACTICAL_DIVISION
JOHNNY BMAD
AUTONOMOUS_DEPLOYMENT_UNIT
Automates the BMAD implementation phase, one epic at a time. Inspired by Ralph.
npm install -g @webeleon/johnny-bmad
cd your-bmad-project
johnny-bmad
That's it. Johnny will:
| Option | Short | Description |
|---|---|---|
--resume |
-r |
Auto-resume from saved state without prompting |
--verbose |
-v |
Enable debug output for troubleshooting |
--max-iterations N |
-m N |
Max dev-review cycles per story (default: 10) |
--yolo |
-y |
Auto-complete stories when max iterations reached |
--help |
-h |
Show help message |
johnny-bmad # Start fresh or prompt to resume
johnny-bmad --resume # Auto-resume from last session
johnny-bmad -v # Verbose output for debugging
johnny-bmad -m 5 # Limit to 5 dev-review cycles
johnny-bmad --yolo # YOLO mode: auto-mark done at max iterations
johnny-bmad -m 3 -y # 3 iterations max, auto-complete if stuck
_bmad/ folderclaude command in PATH)Stories loop through dev -> review until the reviewer marks them done. Default max is 10 iterations per story, then you're prompted to continue, skip, or abort. Use --yolo to auto-complete stuck stories.
| Agent | Model | Purpose |
|---|---|---|
| SM Agent | opus | Check sprint status, initialize planning |
| Story Creator | opus | Create detailed story files with acceptance criteria |
| Dev Agent | sonnet | Implement the story |
| Reviewer | opus | Code review, mark story done when complete |
Progress saves to .johnny-bmad-state.json. If interrupted:
johnny-bmad --resume # Pick up where you left off
The tool expects this structure:
your-project/
├── _bmad/
│ └── bmm/
│ └── config.yaml # Project configuration
├── _bmad-output/
│ ├── planning-artifacts/
│ │ └── epic-*.md # Epic definitions
│ └── implementation-artifacts/
│ ├── sprint-status.yaml # Sprint state
│ └── story-*.md # Story files
git clone https://github.com/webeleon/johnny-bmad.git
cd johnny-bmad
bun install
bun run dev # Watch mode
bun run build # Build to dist/
bun test # Run tests