🚀 Transformative Evolution: From Vanilla BMAD to Next Method
🧠 PHILOSOPHICAL FOUNDATION:
- Transcends traditional methodology through emergent intelligence
- Replaces explicit choice with contextual awareness and flow state
- Embodies Zen principles: present-moment focus and trust in emergence
- Moves from 20th-century deterministic thinking to 21st-century adaptive intelligence
⚡ CORE INNOVATION:
- Standalone 'start'/'init' commands for project initialization
- Intelligent workflow orchestration without cognitive load
- Context-aware development guidance through iteration
- Flow state optimization through choice elimination
🔄 THE PARADOX OF CHOICE RESOLVED:
- Vanilla BMAD: 'Choose wisely from all tools'
- Next Method: 'Use the next tool, let wisdom emerge through use'
- From comprehensive planning to emergent architecture
- From static frameworks to adaptive, context-aware systems
🎯 IMPLEMENTATION:
- Add start/init commands for project initialization
- Enhance CLI with philosophical workflow design
- Integrate context management and intelligent suggestions
- Maintain .next-context.json in .gitignore for clean collaboration
This represents not just a technical enhancement, but a fundamental shift in how we approach software development - from deterministic planning to emergent, contextually intelligent iteration.
- Add NEXT-METHOD CLI with intelligent workflow orchestration
- Implement context-aware project suggestions and auto-execution
- Create comprehensive documentation in docs/next-method/
- Update package.json with next command and scripts
- Maintain full BMAD-METHOD compatibility and features
- Change command pattern from 'next next' to single 'next'
- Add demo script and implementation documentation
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>
* feat: add support for Crush IDE configuration and commands
* fix: update Crush IDE instructions for clarity on persona/task switching
---------
Co-authored-by: Brian <bmadcode@gmail.com>
- Add missing semver dependency to installer package.json
- Configure semantic-release to use correct channels (beta/latest)
- This ensures beta releases publish to @beta tag correctly
* Add update-check command
* Adding additional information to update-check command and aligning with cli theme
* Correct update-check message to exclude global
* feat: install Cursor rules to subdirectory
Implement feature request #376 to avoid filename collisions and confusion
between repo-specific and BMAD-specific rules.
Changes:
- Move Cursor rules from .cursor/rules/ to .cursor/rules/bmad/
- Update installer configuration to use new subdirectory structure
- Update upgrader to reflect new rule directory path
This keeps BMAD Method files separate from existing project rules,
reducing chance of conflicts and improving organization.
Fixes#376
* chore: correct formatting in cursor rules directory path
---------
Co-authored-by: Stefan Klümpers <stefan.kluempers@materna.group>
Downgrade chalk, inquirer, and ora in tools/installer to CommonJS-compatible versions:
- chalk: ^5.4.1 -> ^4.1.2
- inquirer: ^12.6.3 -> ^8.2.6
- ora: ^8.2.0 -> ^5.4.1
Resolves 'is not a function' errors caused by ESM/CommonJS incompatibility.
* feat(cli): move flatten command to installer and update docs
Refactor the flatten command from tools/cli.js to tools/installer/bin/bmad.js for better integration. Add support for custom input directory and improve error handling. Update documentation in README.md and working-in-the-brownfield.md to reflect new command usage. Also clean up package-lock.json and add it to .gitignore.
* chore: update gitignore and add package-lock.json for installer tool
Remove package-lock.json from root gitignore since it's now needed for the installer tool
Add package-lock.json with dependencies for the bmad-method installer
---------
Co-authored-by: Devin Stagner <devin@blackstag.family>
* fix: Update console.log for user-guide.md install path
Changed
IMPORTANT: Please read the user guide installed at docs/user-guilde.md
to
IMPORTANT: Please read the user guide installed at .bmad-core/user-guide.md
WHY: the actual install location of the user-guide.md is in the .bmad-core directory.
* chore: remove formatting configs and clean up gitignore
- Delete husky pre-commit hook and prettier config files
- Remove VS Code chat/copilot settings
- Reorganize and clean up gitignore entries
Abd Shomad
Brian Madison
Jonathan Borgwing
Brian, with AI
manjaroblack
github-actions[bot]
Thiago Freitas
cecil-the-coder
Aaron
Stefan Klümpers
semantic-release-bot
circus
Houston Zhang
Mbosinwa Awunor
Jorge Castillo