This commit refactors the monolithic implement-story-with-review.md into focused, reusable task components to address context window concerns and improve maintainability.
New modular task structure:
- story-analysis.md (40 lines): Handles codebase search, dependency analysis, and complexity assessment
- internal-review-process.md (30 lines): Manages 6-criteria code review workflow
- memory-synthesis.md (50 lines): Extracts and validates learnings into project memory
- implement-story-with-review.md (40 lines): Simplified orchestrator that coordinates sub-tasks
Key benefits:
- Minimal context loading: Each task loads only necessary information
- Reusability: Sub-tasks can be used independently or in other workflows
- Maintainability: Easier to update individual components without affecting others
- IDE compatibility: Better support for tools with short context windows like Cursor
- Separation of concerns: Clear boundaries between analysis, review, and synthesis phases
Updated dev agent dependencies to include all new modular tasks while maintaining full workflow functionality and backward compatibility.
This commit introduces a configurable date check option to optimize the workflow for different AI environments.
New configuration:
- checkCurrentDate: false (default) - Skip date retrieval when current date is available in system context
- checkCurrentDate: true - Explicitly retrieve current date via tool call
Key improvements:
- Eliminates redundant date tool calls in environments where current date is injected into system prompt
- Maintains backward compatibility with default false setting
- Provides flexibility for environments that need explicit date retrieval
- Updated dev agent startup to load the new configuration setting
This optimization reduces unnecessary tool calls while maintaining the temporal context functionality for environments that require it, improving overall workflow efficiency.
This commit enhances the dependency analysis workflow to intelligently determine when internet research is critical versus optional, preventing the model doesn't know what it doesn't know problem.
Key improvements:
- Version Criticality Analysis: Compares package.json versions against model training cutoff to identify potentially unknown libraries
- Smart Fallback Logic: Distinguishes between critical research (newer versions, latest specifiers) and optional research (general best practices)
- Risk-Aware Halting: Stops execution for critical version mismatches with clear explanation of risks
- User Choice Preservation: Allows informed decisions about proceeding without current knowledge
Critical triggers include:
- Package versions newer than model training data
- latest/^ version specifiers for major dependencies
- Completely new frameworks not in training data
- Major version bumps requiring migration knowledge
This prevents implementation failures due to outdated patterns while maintaining workflow efficiency for routine development tasks.
This commit enhances the internal review process by adding three critical review criteria that align with industry-standard automated code review practices.
New review criteria:
- **Security Vulnerabilities**: Checks for input validation, authentication issues, data exposure, and hardcoded secrets
- **Performance Impact**: Identifies N+1 queries, memory leaks, inefficient algorithms, and excessive resource usage
- **Architecture Compliance**: Validates separation of concerns, SOLID principles, and established architectural patterns
The expanded criteria bring BMAD's review process in line with tools like SonarQube and ESLint, ensuring comprehensive code quality assessment across functionality, security, performance, and architecture dimensions.
Updated review summary template to capture learnings from all six criteria, providing richer project memory synthesis and better guidance for future development.
This commit updates the complexity assessment system from a 1-10 scale to the industry-standard Fibonacci scale (1, 2, 3, 5, 8, 13), aligning BMAD with Agile best practices.
Key changes:
- Updated agentThresholdStory from 6 to 5 (Fibonacci equivalent)
- Updated agentThresholdTask from 7 to 8 (Fibonacci equivalent)
- Added Fibonacci complexity guidelines to help agents make consistent assessments
- Modified task instructions to reference Fibonacci scale instead of 1-10
This change ensures consistency with industry standards that most development teams already understand, while maintaining the same relative complexity thresholds for triggering review processes.
This commit enhances the resilience of the `implement-story-with-review` task by adding a graceful fallback mechanism for when the agent cannot access the internet.
Previously, the "Dependency & Standards Analysis" step assumed that an internet connection was available to research modern best practices. This would cause the agent to fail or hang in offline or restricted environments.
The workflow has been updated as follows:
1. The agent now *attempts* to perform the internet search.
2. If the search fails due to a lack of connectivity, it will:
- Inform the user of the situation.
- Ask the user if they want to enable access or if it should proceed using only its existing training data.
- Halt and wait for explicit user confirmation before continuing.
This change prevents the agent from getting stuck and empowers the user to make an informed decision, making the entire process more robust and suitable for a wider range of development environments.
This commit refactors the `implement-story-with-review` task to close a critical logic flaw.
Previously, the task-level complexity check was only performed if the entire story was already in "Review Mode." This created a blind spot where a complex task could go unreviewed if it was part of a story deemed "simple."
The workflow has been updated to a single, unified execution path:
1. The initial story-level complexity assessment now only serves to log a general "state of caution."
2. The task-level complexity check against `agentThresholdTask` is now **mandatory for every task in every story**, regardless of the initial mode.
This ensures that no complex task can be implemented without triggering the internal review process, making the agent's workflow more robust and reliable.
This major feature evolves the Developer Agent from a simple task executor into a context-aware engineer by introducing a new, intelligent workflow and a persistent project memory system.
The new workflow, encapsulated in the `implement-story-with-review` task, consists of two primary phases:
1. **Analysis & Review Phase:**
- Before implementation, the agent proactively analyzes the codebase using semantic search to find reusable patterns and components.
- It assesses story and task complexity against configurable thresholds (`agentThresholdStory`, `agentThresholdTask` in `core-config.yml`).
- For complex tasks, it enters a "Review Mode" and uses an internal "Reviewer" persona to self-critique its own code for duplication, errors, and standards alignment before proceeding.
2. **Memory Synthesis Phase:**
- Upon successfully completing a story, the agent automatically performs a holistic scan of its own developer notes.
- It distills explicit "Lessons Learned" and implicit knowledge into general, actionable rules.
- These memories are validated against existing knowledge to prevent contradictions and are then intelligently upserted into a new, shared `bmad-project-memory.md` file.
**Supporting System Changes:**
- **Orchestrator:** The `bmad-orchestrator` now loads the `bmad-project-memory.md` file on startup, providing all agents with shared, evolving project context.
- **Installer:** The BMAD installation process has been updated to correctly scaffold the new `.bmad-core/data/bmad-project-memory.md` file into new projects, ensuring the feature is available out-of-the-box.
This creates a powerful, real-time learning loop, enabling the AI team to improve and adapt based on project-specific experience, leading to higher-quality and more consistent code.
- Add markdownExploder setting to core-config.yml
- Update shard-doc task to use md-tree command when enabled
- Implement proper fallback handling when tool is unavailable
- Update core-config structure to remove nested wrapper
- Fix field naming to use camelCase throughout
* 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>
This commit represents a significant milestone in the BMAD-METHOD v4 framework restructuring effort, focusing on cleaning up legacy v3 content and enhancing IDE agent configurations.
Key Changes:
1. Legacy Content Cleanup:
- Removed entire _old/ directory containing v3 framework content (55 files, ~6900 lines)
- Deleted deprecated checklists, personas, tasks, and templates from v3
- Cleaned up obsolete web orchestrator configurations
2. IDE Agent Enhancements:
- Added new IDE agent configurations for all major roles:
* analyst.ide.md - Business Analyst agent
* architect.ide.md - Architecture specialist agent
* pm.ide.md - Product Manager agent
* po.ide.md - Product Owner agent
* devops.ide.md - DevOps/Platform Engineer agent (replacing devops-pe.ide.md)
- Updated dev.ide.md with improved structure and commands
- Enhanced sm.ide.md with proper persona naming (Bob)
3. New Persona Definitions:
- Added missing persona files: dev.md, devops.md, qa.md
- Standardized persona format across all roles
4. QA Agent Addition:
- Added qa.yml configuration for Quality Assurance agent
5. IDE Integration Improvements:
- Added .claude/commands/ directory for Claude Code command definitions
- Added .cursor/rules/ for Cursor IDE integration
- Created agent-switcher.ide.md utility for seamless agent switching
6. Command Updates:
- Renamed /exit command to /exit-agent for clarity and consistency
7. Build System Updates:
- Minor fixes to web-builder.js for improved bundle generation
This restructuring aligns with the v4 architecture goals of modularity, reusability, and improved developer experience across different IDE environments.
Authored-By: BMad
kevlingo
Brian Madison
titocr
Brian