Add Context7 MCP integration to provide agents with current, version-specific
documentation for libraries and frameworks, eliminating outdated code generation.
- Create comprehensive Context7 task (bmad-core/tasks/context7-docs.md)
- Add Context7 configuration to core-config.yaml with command templates
- Enhance dev agent with implementation-focused documentation access
- Enhance architect agent with architecture pattern documentation
- Enhance researcher agent with technical domain research capabilities
- Follow proven Gemini CLI integration pattern for consistency
- Support six documentation modes: library, API, patterns, troubleshooting, etc.
- Include agent-specific usage guidance and safety measures
Agents can now use `*context7-docs {technology}` to get current documentation
by including "use context7" in their prompts, ensuring accurate and up-to-date
implementation guidance for architecture decisions and code patterns.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
Combined Option A + B implementation providing comprehensive large context analysis:
Core Integration:
- Add gemini-analysis.md task for massive context window operations
- Configure geminiCli settings in core-config.yaml with safety controls
- Support @file/directory syntax and --all-files mode for project-wide analysis
- Implement configurable approval modes and timeout protections
Agent Capabilities:
- Add *gemini-analyze command to analyst, architect, and dev agents
- Enable large codebase discovery, architecture analysis, and debugging
- Support feature verification and pattern discovery across entire projects
- Maintain read-only default with approval prompts for modifications
Team Configurations:
- Create team-gemini-analysis.yaml for specialized large context work
- Include comprehensive command templates and usage examples
- Integrate with existing fullstack and development workflows
Documentation & Safety:
- Update CLAUDE.md with comprehensive Gemini CLI usage guide
- Provide command templates for common analysis patterns
- Include safety measures, path validation, and error handling
- Document integration patterns with existing BMAD workflow
The system enables analysis of large codebases that exceed normal context limits
while maintaining BMAD's safety-first approach and task-based architecture.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add research-coordinator agent with multi-perspective coordination capabilities
- Add adaptable researcher agent with domain-specific specialization profiles
- Implement unified request-research task for agent-to-research communication
- Add research logging and indexing system in docs/research/
- Include web search capabilities and configurable team size (default 3)
- Update analyst, architect, and pm agents with research command integration
- Add research team configuration and integrate into fullstack team
- Implement research synthesis templates and quality assurance checklists
- Add comprehensive research methodologies and domain expertise documentation
The system enables any agent to request specialized research through standardized
task interface, with research coordinator spawning domain experts and synthesizing
findings into actionable reports while maintaining indexed research log.
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* 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
- 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.
- Remove 'root' property from YAML when building web bundles
- Remove 'IDE-FILE-RESOLUTION' and 'REQUEST-RESOLUTION' properties
- Filter out IDE-specific activation instructions
- Keep agent header minimal for web bundles
- Ensures web bundles are clean of IDE-specific configuration
🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
* feat: add expansion pack installation system with game dev and infrastructure expansion packs
- Added expansion pack discovery and installation to BMAD installer
- Supports interactive and CLI installation of expansion packs
- Expansion pack files install to destination root (.bmad-core)
- Added game development expansion pack (.bmad-2d-phaser-game-dev)
- Game designer, developer, and scrum master agents
- Game-specific templates, tasks, workflows, and guidelines
- Specialized for Phaser 3 + TypeScript development
- Added infrastructure devops expansion pack (.bmad-infrastructure-devops)
- Platform engineering agent and infrastructure templates
- Expansion pack agents automatically integrate with IDE rules
- Added list:expansions command and --expansion-packs CLI option
🤖 Generated with Claude Code
Co-Authored-By: Claude <noreply@anthropic.com>
* alpha expansion packs and installer update to support installing expansion packs optionally
* node20
---------
Co-authored-by: Brian Madison <brianmadison@Brians-MacBook-Pro.local>
Co-authored-by: Claude <noreply@anthropic.com>