NEXT_SESSION.md is useful for testing but should not be in the
development branch. Can be recreated in a separate testing branch
if needed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add blank line before list in Error Handling section
- Improve markdown compliance
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add comprehensive DEVELOPMENT_APPROACH.md document
- Document direct development vs BMB create-module comparison
- Include compliance matrix with BMAD v6 standards
- Add recommendations for future module development
- Fix markdown formatting and URL links in README
- Add new doc to Documentation section
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add practical examples demonstrating VCS-agnostic adaptation:
- vcs-adaptation-examples.md: 6 real-world scenarios (GitHub Flow,
GitFlow, No VCS, SVN, Trunk-Based, Multi-VCS)
- vcs-detection-implementation.py: Reference implementation of Git
workflow auto-detection with confidence scoring
- examples/README.md: Guide to using examples and integration
Examples demonstrate "Detection as a HINT, not a DECISION" principle
with evidence-based suggestions and user confirmation.
Part 4/5 of BMVCS migration (#661)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add comprehensive documentation for VCS-agnostic approach:
- VCS_AGNOSTIC_PRINCIPLES.md: Core philosophy and 10 principles
- VCS_AGNOSTIC_PROPOSAL.md: Implementation approach and examples
- VCS_DETECTION_CONFIDENCE.md: Auto-detection confidence scoring
- docs/README.md: Documentation overview and quick start
Documentation explains how BMAD adapts to any VCS (Git, SVN, Perforce,
or no VCS) with appropriate terminology and workflow patterns.
Part 3/5 of BMVCS migration (#661)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add 5 VCS adaptation templates for different workflows:
- git-github-flow.yaml: Simple feature branches (40% of users)
- git-gitflow.yaml: Structured releases (20% of users)
- git-trunk-based.yaml: Continuous deployment (15% of users)
- no-vcs.yaml: Prototypes and one-time scripts (5% of users)
- custom-generic.yaml: Custom/legacy VCS systems (10% of users)
Templates support VCS-agnostic artifact generation across all BMAD agents.
Part 2/5 of BMVCS migration (#661)
Completes core VCS discovery functionality
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Port discover-vcs.md from PR #582 (187 lines)
- Port create-vcs-adapted-doc.md from PR #583 (165 lines)
- Add validate-vcs-config.md task (73 lines new)
- Add installer.js for module setup (26 lines)
Part 2/5 of BMVCS migration (#661) - Tasks Complete
Note: VCS templates to be added in next commit after proper extraction
Next: Manually create 5 VCS templates with valid YAML
- Created agent-activation-web.xml with bundled file access instructions
- Updated web-bundler to inject web activation into all agent bundles
- Agents now understand how to access <file> elements instead of filesystem
- Includes workflow execution instructions for bundled environments
- Generated new web bundles with activation blocks
* feat: add OpenCode integration implementation plan for BMAD-METHOD
* installer(opencode): add OpenCode target metadata in install.config.yaml
* chore(deps): add comment-json for JSONC parsing in OpenCode integration
* feat(installer/opencode): implement setupOpenCode with minimal instructions merge and BMAD-managed agents/commands
* feat(installer): add OpenCode (SST) to IDE selector and CLI --ide help
* fix(opencode): align generated opencode.json(c) with schema (instructions as strings; agent.prompt; command.template; remove unsupported fields)
* feat(installer): enhance OpenCode setup with agent selection and prefix options
* fix: update configuration file references from `bmad-core/core-config.yaml` to `.bmad-core/core-config.yaml` across multiple agent and task files for consistency and clarity.
* refactor: streamline OpenCode configuration prompts and normalize instruction paths for agents and tasks
* feat: add tools property to agent definitions for enhanced functionality. Otherwise opencode consders the subagents as readonly
* feat: add extraction of 'whenToUse' from agents markdown files for improved agent configuration in opencode
* feat: enhance task purpose extraction from markdown files with improved parsing and cleanup logic
* feat: add collision warnings for non-BMAD-managed agent and command keys during setup
* feat: generate and update AGENTS.md for OpenCode integration with agent and task details
* feat: add compact AGENTS.md generator and JSON-only integration for OpenCode
* chore(docs): remove completed OpenCode integration implementation plans
* feat: enable default prefixes for agent and command keys to avoid collisions
* fix: remove unnecessary line breaks in 'whenToUse' descriptions for QA agents to mathc the rest of the agents definitions and improve programatic parsing of whenToUse prop
* fix: update OpenCode references to remove 'SST' for consistency across documentation and configuration
* fix: update agent mode from 'subagent' to 'all' for consistency in agent definitions
* fix: consolidate 'whenToUse' description format for clarity and consistent parsing
* fix: simplify title in coding standards section of brownfield architecture template
* fix: update section titles in brownfield architecture template for clarity
* Godot Game Dev expansion pack for BMAD
* Workflow changes
* Workflow changes
* Fixing config.yaml, editing README.md to indicate correct workflow
* Fixing references to config.yaml, adding missing QA review to game-dev agent
* More game story creation fixes
* More game story creation fixes
* Adding built web agent file
* - Adding ability for QA agent to have preloaded context files similar to Dev agent.
- Fixing stray Unity references in game-architecture-tmpl.yaml
---------
Co-authored-by: Brian <bmadcode@gmail.com>
* feat: add iflow cli support
* chore: update project dependencies and development tooling (#508)
- 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>
* refactor: refactor by format
---------
Co-authored-by: Kayvan Sylvan <kayvan@sylvan.com>
Co-authored-by: Kayvan Sylvan <kayvan@meanwhile.bm>
Co-authored-by: PinkyD <paulbeanjr@gmail.com>
Co-authored-by: Brian <bmadcode@gmail.com>
This change modifies the .gitignore file to ensure the cursor file is properly ignored by removing the incorrect entry and adding the correct one. This helps maintain a cleaner repository by preventing unnecessary files from being tracked.
Co-authored-by: Brian <bmadcode@gmail.com>
- Added support for a new optional `.bmad-flattenignore` file to allow users to specify additional files to exclude from the flattened XML output.
- Updated README and documentation to reflect the new feature and provide examples for usage.
- Modified ignore rules to incorporate patterns from the `.bmad-flattenignore` file after applying `.gitignore` rules.
Benefits:
- Greater flexibility in managing file exclusions for AI model consumption.
* feat: add Augment Code IDE support with multi-location installation options
- Add Augment Code to supported IDE list in installer CLI and interactive prompts
- Configure multi-location setup for Augment Code commands:
- User Commands: ~/.augment/commands/bmad/ (global, user-wide)
- Workspace Commands: ./.augment/commands/bmad/ (project-specific, team-shared)
- Update IDE configuration with proper location handling and tilde expansion
- Add interactive prompt for users to select installation locations
- Update documentation in bmad-kb.md to include Augment Code in supported IDEs
- Implement setupAugmentCode method with location selection and file installation
This enables BMAD Method integration with Augment Code's custom command system,
allowing users to access BMad agents via /agent-name slash commands in both
global and project-specific contexts.
* Added options to choose the rule locations
* Update instruction to match with namespace for commands
* Update instruction to match with namespace for commands
* Renamed Augment Code to Auggie CLI (Augment Code)
---------
Co-authored-by: Hau Vo <hauvo@Haus-Mac-mini.local>
Co-authored-by: Brian <bmadcode@gmail.com>
- 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
Serhii
Brian Madison
Murat K Ozcan
Murat Ozcan
lihangmissu
Javier Gomez
Daniel Dabrowski
sjennings
liyuyun-lyy
Armel BOBDA
Drilmo
VansonLeung
Yoav Gal
Yuewen Ma
Hau Vo
Mikhail Romanov