- Enhanced TDD expansion pack README with production-ready status
- Complete TDD evaluation report with 9.5/10 rating
- Calculator demo documentation and findings
- Pull request template with comprehensive contribution details
This adds essential documentation for the TDD expansion pack based on
successful evaluation using a working calculator project that achieved:
- 100% test coverage with 21 comprehensive test cases
- Complete Red-Green-Refactor TDD cycle documentation
- Seamless integration with existing BMAD framework
- Production-ready status with zero breaking changes
Ready for production deployment as optional expansion pack.
- Organized all TDD-related files into expansion pack structure
- Created comprehensive installation guide (INSTALL.md)
- Added migration guide for existing projects (MIGRATION.md)
- Included all TDD components:
- Enhanced QA and Dev agent configurations
- TDD-specific tasks (write-failing-tests, tdd-implement, tdd-refactor)
- Quality gates and CI/CD templates
- Guard scripts for TDD validation
- Complete demo example
The expansion pack is ready for contribution to BMAD-METHOD repository.
It maintains full backward compatibility and can be enabled/disabled
through configuration.
- Created expansion pack directory structure
- Added README with comprehensive documentation
- Prepared directories for agents, tasks, templates, scripts, and examples
This expansion pack adds TDD capabilities to the BMAD-METHOD, including:
- Enhanced QA and Dev agents for TDD phases
- TDD-specific commands and workflows
- Quality gates and CI/CD integration
- Example implementations
Add example story for User Email Validation TDD workflow:
- Complete story with acceptance criteria in Gherkin format
- Technical requirements and test plan with test IDs
- TDD phase progress tracking (currently red)
- Implementation tasks for Dev agent
- Directory structure for JS and Python demo implementations
This demo story provides teams with a practical example to reproduce
the red-green-refactor TDD cycle using BMAD framework and methodology.
- Update QA agent (qa.md) with TDD Red phase commands:
- *tdd-start: Initialize TDD for story
- *write-failing-tests: Generate failing tests (Red phase)
- *tdd-refactor: Participate in refactor with safety checks
- Add TDD methodology and test isolation principles
- Update Dev agent (dev.md) with TDD Green/Refactor phase commands:
- *tdd-implement: Implement minimal code to pass tests (Green phase)
- *make-tests-pass: Iterative test-driven implementation
- *tdd-refactor: Collaborate on safe refactoring
- Add TDD discipline and test-first validation rules
- Enhance test-design.md with TDD-first support:
- Add TDD mode for Red phase test design
- Mocking strategy selection matrix (mock/fake/stub)
- Smallest-next-test principle
- Deterministic test data strategies
- Create TDD quality gates template (tdd-quality-gates.md):
- Phase-specific gate criteria (Red/Green/Refactor)
- Pass/Fail/Concerns criteria per phase
- Recovery procedures for gate failures
- Integration with existing BMAD quality gates
All agents now support both traditional and TDD workflows.
TDD features are conditionally available when tdd.enabled=true.
- Remove IDE-specific Codex documentation from end of README
- This content was oddly placed after the footer
- IDE-specific docs should be in separate documentation
- CI/CD disabled by default in forks to conserve resources
- Users can enable via ENABLE_CI_IN_FORK repository variable
- Added comprehensive Fork Guide documentation
- Updated README with Contributing section
- Created automation script for future implementations
Benefits:
- Saves GitHub Actions minutes across 1,600+ forks
- Cleaner fork experience for contributors
- Full control for fork owners
- PR validation still runs automatically
BREAKING CHANGE: CI/CD no longer runs automatically in forks.
Fork owners must set ENABLE_CI_IN_FORK=true to enable workflows.
Co-authored-by: Brian <bmadcode@gmail.com>
Co-authored-by: PinkyD <paulbeanjr@gmail.com>
- Change 'Dependencies map to root/type/name' to 'Dependencies map to {root}/{type}/{name}'
- Fixes path resolution issue where 'root' was treated as literal directory name
- Ensures proper variable interpolation for dependency file loading
- Resolves agent inability to find core-config.yaml and other project files
- Update various direct and transitive project dependencies.
- Remove the circular `bmad-method` self-dependency.
- Upgrade ESLint, Prettier, Jest, and other dev tools.
- Update semantic-release and related GitHub packages.
Co-authored-by: Kayvan Sylvan <kayvan@meanwhile.bm>
This fixes a regression bug where the flatten command would fail with an
error message even when valid arguments were provided.
The bug was:
- First introduced in commit 0fdbca7
- Fixed in commit fab9d5e (v5.0.0-beta.2)
- Accidentally reintroduced in commit ed53943
The else branch at lines 130-134 was incorrectly handling the case when
users provided arguments, showing a misleading error about
'no arguments provided' when arguments were actually present.
Fixes all flatten command variations:
- npx bmad-method flatten
- npx bmad-method flatten --input /path
- npx bmad-method flatten --output file.xml
- npx bmad-method flatten --input /path --output file.xml
Co-authored-by: Brian <bmadcode@gmail.com>
- Alphabetized all commands in agent files while maintaining help first and exit last
- Alphabetized all dependency categories (checklists, data, tasks, templates, utils, workflows)
- Alphabetized items within each dependency category across all 10 core agents:
- analyst.md: commands and dependencies reorganized
- architect.md: commands and dependencies reorganized
- bmad-master.md: commands and dependencies reorganized, fixed YAML parsing issue
- bmad-orchestrator.md: commands and dependencies reorganized
- dev.md: commands and dependencies reorganized
- pm.md: commands and dependencies reorganized
- po.md: commands and dependencies reorganized
- qa.md: commands and dependencies reorganized
- sm.md: commands and dependencies reorganized
- ux-expert.md: commands and dependencies reorganized
- Fixed YAML parsing error in bmad-master.md by properly quoting activation instructions
- Rebuilt all agent bundles and team bundles successfully
- Updated expansion pack bundles including new creative writing agents
This improves consistency and makes it easier to locate specific commands and dependencies
across all agent configurations.
* Add Creative Writing expansion pack
- 10 specialized writing agents for fiction and narrative design
- 8 complete workflows (novel, screenplay, short story, series)
- 27 quality checklists for genre and technical validation
- 22 writing tasks covering full creative process
- 8 professional templates for structured writing
- KDP publishing integration support
* Fix bmad-creative-writing expansion pack formatting and structure
- Convert all agents to standard BMAD markdown format with embedded YAML
- Add missing core dependencies (create-doc, advanced-elicitation, execute-checklist)
- Add bmad-kb.md customized for creative writing context
- Fix agent dependency references to only include existing files
- Standardize agent command syntax and activation instructions
- Clean up agent dependencies for beta-reader, dialog-specialist, editor, genre-specialist, narrative-designer, and world-builder
---------
Co-authored-by: Brian <bmadcode@gmail.com>
Previously users had to manually type the full path or run pwd to get
the current directory when installing BMad. Now the installer prefills
the current working directory as the default, improving UX.
Co-authored-by: its-brianwithai <brian@ultrawideturbodev.com>
- Replace old semantic-release documentation with new simplified system
- Document command line release workflow (npm run release:*)
- Explain automatic release notes generation and categorization
- Add troubleshooting section and preview functionality
- Reflect current single @stable tag installation approach
- Allow workflow to continue even if push to main fails
- This is expected behavior with protected branches
- NPM publishing and GitHub releases will still work
- Fix version-bump.js to actually update package.json version
- Add tag existence check to prevent duplicate tag errors
- Remove semantic-release dependency from version bumping
- Add automatic release notes generation from commit history
- Categorize commits into Features, Bug Fixes, and Maintenance
- Include installation instructions and changelog links
- Add preview-release-notes script for testing
- Update GitHub release creation to use generated notes
vforvaick
Brian Madison
Brian
Jonathan Borgwing
Bragatte
Piatra Automation
Wang-tianhao
Chris Calo
Kayvan Sylvan
circus
DrBalls
Anthony
Brian, with AI
manjaroblack