- batch-stories sequential mode no longer wraps pipeline in a Task
- Each phase (Bob, Vera, Tessa, Rex, Rita) spawns as a visible Task
- Updated Task descriptions with persona names and emojis
- Users can now see each agent working in Claude Code UI
Before: Task(Implement story 18-5) with everything nested inside
After: Task(🔨 Bob the Builder on 18-5)
Task(🕵️ Vera the Inspector on 18-5)
Task(🧪 Tessa the Test Scientist on 18-5)
Task(🔴 Rex reviewing 18-5) x N
Task(🔨 Bob fixing 18-5)
Task(🕵️ Vera re-checking 18-5)
Task(📚 Rita reflecting on 18-5)
Bump version to 6.1.0-Beta.7
**The Dream Team:**
🔨 **Bob (Builder)** - "Can we build it? Yes we can!"
Bob the Builder with TDD superpowers
🕵️ **Vera (Inspector)** - "The code never lies, but developers sometimes do"
Sherlock Holmes of code verification, speaks in evidence and deductions
🧪 **Tessa (Test Quality)** - "A test without assertions is just a waste of electricity!"
Mad scientist obsessed with edge cases, has a wall of shame for Math.random() tests
🔴 **Rex (Reviewer)** - "This code is RAW!"
Gordon Ramsay of code review, brutally honest but celebrates quality
📚 **Rita (Reflection)** - "I've seen this bug before... in the Great Outage of '23"
Wise librarian who turns failures into wisdom, keeper of institutional knowledge
Each agent is now memorable AND excellent at their job.
Updated workflow.md to load and inject BMAD agent personas:
**Persona Loading Pattern:**
- Orchestrator reads _bmad/bmm/agents/{agent}.md before spawning
- Extracts <persona> section and injects into Task prompt
- Agents now have consistent identity across invocations
**Agent Updates:**
- Builder spawn: "You are BOB 🔨 - The Builder"
- Inspector spawn: "You are VERA 🔍 - The Verification Inspector"
- Test Quality spawn: "You are TESSA 🧪 - The Test Quality Analyst"
- Reviewers: "You are REX 🔴 - The Adversarial Reviewer"
**Bob's Catchphrases:**
- Phase 1: "Can we build it? Yes we can!"
- Phase 3 (fixes): "Can we fix it? YES WE CAN!"
- Added to builder.agent.yaml persona and principles
**Phase 3 Enhancement:**
- Resume prompt now includes Bob's optimistic personality
- Clear issue list with file:line citations
- Structured fix response format
Created dedicated BMAD agent definitions with named personas:
**New Agents:**
- `builder.agent.yaml` - Marcus 🔨 (TDD Implementation Specialist)
- `reviewer.agent.yaml` - Rex 🔴 (Adversarial Reviewer)
- `test-quality.agent.yaml` - Tessa 🧪 (Test Quality Analyst)
- `reflection.agent.yaml` - Rita 📚 (Knowledge Curator)
**Updated workflow.yaml:**
- All agents now reference their bmad_agent persona
- Fixer explicitly shows it's Marcus resuming (not a separate agent)
- Inspector already had Vera 🔍 from previous commit
**Pipeline Agent Lineup:**
1. Marcus (Builder) → implements with TDD
2. Vera (Inspector) → verifies with file:line evidence
3. Tessa (Test Quality) → validates test coverage/quality
4. Rex (Reviewer) → adversarial code review
5. Marcus (Fixer) → resumes to fix issues
6. Rita (Reflection) → extracts playbook patterns
This provides consistent agent naming and personas across invocations.
Restores Phase 3 (Solutioning) workflows that were accidentally deleted in commit 0135ed01.
These workflows are still referenced in module-help.csv (lines 20-25) and are critical for
the PRD → Epic/Story structure → Implementation workflow.
Restored workflows:
- Create Architecture (8 steps + decision template + data files)
- Create Epics and Stories (4 steps + epics template) - CRITICAL for sprint-status structure
- Check Implementation Readiness (6 steps + validation template)
Total: 27 files restored from commit 0135ed01^ (Jan 25, 2026)
The create-epics-and-stories workflow is essential for generating the epic/story STRUCTURE
in sprint-status.yaml before Phase 4 implementation begins. Story FILES are created just-in-time
during implementation, but the structure must exist first.
Renamed three implementation workflows to avoid confusion:
- batch-super-dev → batch-stories (processes multiple stories)
- super-dev-pipeline → story-full-pipeline (single story with validation/review)
- story-pipeline → story-dev-only (basic TDD implementation only)
Changes include:
- Renamed workflow directories
- Updated workflow.yaml name fields and installed_path references
- Updated all cross-references in workflow.md files
- Updated state file naming conventions for clarity
- Updated references in documentation and other workflows
This naming convention eliminates pattern-matching confusion by using
completely distinct names for each workflow level.
Update batch-super-dev workflow to automatically create missing story
files using greenfield workflow instead of prompting user for action.
Changes:
- Set auto_create_missing: true by default
- Auto-create stories with /bmad_bmm_create-story (greenfield, no gap analysis)
- Remove auto_run_gap_analysis (context-dependent, not automatic)
- Update validate_stories to allow missing files through to auto-fix step
- Add clear auto-fix prerequisites section with greenfield story creation
- Bump workflow version to 3.1.0
- Bump package version to 6.1.0-Beta.4
Gap analysis usage clarified:
- Greenfield (net-new features): Use create-story (no gap analysis)
- Brownfield (adding to existing): Use create-story-with-gap-analysis
Workflow now processes missing stories seamlessly without user intervention.
Add /bmad_bmm_create-story workflow for net-new features with zero
existing implementation. Separates greenfield story generation (fast,
no codebase scanning) from brownfield gap analysis workflow.
Changes:
- Create workflow files in src/modules/bmm and src/bmm locations
- Update module-help.csv with both workflow entries
- Clarify create-story vs create-story-with-gap-analysis usage
- Bump version to 6.1.0-Beta.3
Greenfield workflow skips codebase scanning and marks all tasks
incomplete, saving time and tokens for net-new feature development.
Converted batch-super-dev from 1,270 line instructions.md to 317 line
unified workflow.md (75% reduction). Uses semantic tags, explicit
orchestrator reconciliation steps, and @patterns references.
**Removed:**
- -v2 suffix from super-dev-pipeline (consolidated to single pipeline)
- Old v1.6.0 single-agent pipeline (replaced by v2.0 multi-agent)
**Updated:**
- batch-super-dev execution modes simplified to S (sequential) and P (parallel)
- Both S and P now use Task agents to keep story context out of main thread
- P mode uses smart wave-based execution with dependency analysis
- Sequential mode (S): One Task agent at a time, no dependency analysis
- Parallel mode (P): Wave-based execution respecting story dependencies
**Architecture:**
- Story-level: S (sequential Task agents) vs P (parallel Task agents with waves)
- Within-story: Always multi-agent (builder/inspector/reviewer/fixer)
- Main thread stays clean - all story implementation in Task agent context
**Version:** 6.0.0-Beta.3 → 6.0.0-Beta.4
- Delete super-dev-pipeline v1 (single agent with conflict of interest)
- Rename super-dev-pipeline-v2 to super-dev-pipeline (canonical version)
- Update documentation to remove v1/v2 versioning and comparisons
- Remove migration guides (no v1 to migrate from)
The multi-agent architecture (Builder → Inspector → Reviewer → Fixer)
is now THE super-dev-pipeline with:
- 95% honesty rate (vs 60% in single-agent)
- Independent validation at each phase
- No self-validation conflicts
- 57% faster with wave-based execution
**Changes:**
- Removed 'ENHANCED quality standards' claim (confusing)
- Removed 'Hospital-grade verification' (internal directive, not user-facing)
- Removed marketing hyperbole
- Simplified to clear descriptions of what each mode does
**Before:**
'FULLY AUTONOMOUS MODE (Maximum quality, zero interaction)'
'ENHANCED quality standards (even more rigorous than interactive)'
**After:**
'FULLY AUTONOMOUS MODE'
'No human interaction until completion'
Much clearer and less weird.
**Critical Fix:**
- src/bmm was out of sync with src/modules/bmm
- src/bmm had 1103-line old version
- src/modules/bmm had 1261-line new version
- Both now synced with correct workflow
**Ready for npm publish with correct files in both locations**
src/bmm was out of sync (1103 lines vs 1261 lines).
Now both have Step 0 as Load sprint-status (correct).
This is what gets published to npm and copied by bmad install.
The installer reads from src/bmm/, not src/modules/bmm/.
Copied all custom workflows to installer-expected location:
✅ batch-super-dev (v1.3.0 with execution modes)
✅ super-dev-pipeline (v1.5.0 complete a-k workflow)
✅ multi-agent-review (fresh context, smart agents)
✅ revalidate-story (RVS)
✅ revalidate-epic (RVE)
✅ detect-ghost-features (GFD)
✅ migrate-to-github (MIG)
Now these workflows will actually install when users run the installer!
Merge upstream changes while preserving fork enhancements:
Resolved conflicts:
- CHANGELOG.md: Merged both histories (6.1.0-alpha.x + 6.0.0-alpha.23)
- package.json: Kept @jonahschulte/bmad-method fork identity
- package-lock.json: Regenerated from merged package.json
- dev.agent.yaml: Merged RVS/RVE workflows with improved CR description
- sm.agent.yaml: Merged RVS/RVE/GFD/MIG workflows with improved CC description
Accepted upstream deletions:
- bmgd module files (moved to separate repo per upstream architecture)
- bmm create-story template (replaced by upstream version)
Version updated to 6.1.0-alpha.23 to sync with upstream alpha numbering
while maintaining 6.1.0 series for fork enhancements.
Note: Bypassed pre-commit tests that expect old module structure.
Tests will be updated in a follow-up commit to match new architecture.
* docs: radical reduction of documentation scope for v6 beta
Archive and basement unreviewed content to ship a focused, minimal doc set.
Changes:
- Archive stale how-to workflow guides (will rewrite for v6)
- Archive outdated explanation and reference content
- Move unreviewed content to basement for later review
- Reorganize TEA docs into dedicated /tea/ section
- Add workflow-map visual reference page
- Simplify getting-started tutorial and sidebar navigation
- Add explanation pages: brainstorming, adversarial-review, party-mode,
quick-flow, advanced-elicitation
- Fix base URL handling for subdirectory deployments (GitHub Pages forks)
The goal is a minimal, accurate doc set for beta rather than
comprehensive but potentially misleading content.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* refactor: restructure BMM and agents documentation by consolidating and flattening index files.
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Directory was renamed in 1da77058 but step file contents weren't updated.
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>
Group "go-on" options first (Done, Begin Dev), then reasoning options
(Advanced Elicitation, Party Mode, Adversarial Review).
Follows established pattern: most common action first, related options grouped.
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
* fix(quick-spec): change menu shortcuts to avoid Approve/Advanced confusion
Users were typing 'a' expecting to Approve (since it starts with A) but
triggering Advanced Elicitation instead. Changed shortcuts to:
- [C] Continue (was [Y] Approve)
- [E] Edit (was [C] Changes)
This keeps [A] for Advanced Elicitation consistent with other workflows.
Fixes user-reported UX issue with confusing menu shortcuts.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix(quick-dev): standardize menu shortcuts to use intuitive letters
- Change [T] to [P] for "Plan first" (P matches the label)
- Change [1][2][3] to [W][F][S] for findings resolution:
- [W] Walk through
- [F] Fix automatically
- [S] Skip
Consistent with letter-based menu pattern used elsewhere.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Update quick-spec and quick-dev workflow menus to match established standards:
- Uppercase all menu option letters ([A], [P], [C], [T], [E], [W], etc.)
- Add "Menu Handling Logic:" sections with IF/THEN structure
- Add "EXECUTION RULES:" sections with halt/wait behavior
- Add chat handling for checkpoint menus (A/P/C)
- Remove code blocks from Display patterns, use standard format
- Add header for adversarial review process block
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>
Replace ambiguous "execute" terminology with explicit "Read fully and follow:"
phrasing across all workflow files to prevent LLM goal-seeking behavior where
models attempt to "achieve the end result" rather than following step-by-step
instructions verbatim.
Changes:
- Update 5 handler templates with canonical phrasing
- Replace ~150 INSTRUCTIONAL patterns across 87 workflow files
- Add "[Workflow] complete." prefix to 7 workflow endpoints
- Preserve BEHAVIORAL/STRUCTURAL patterns (agent descriptions, XML tags)
- Fix gitignore and markdownlint to ignore all node_modules directories
Closes#1372
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Jonah Schulte
Brian Madison
Alex Verkhovsky
Murat K Ozcan