Converted dev-journal-tmpl.md to dev-journal-tmpl.yaml for consistency with
BMAD framework template standards and improved functionality.
YAML Template Features:
- Guided workflow with structured prompting system
- Comprehensive sections for session documentation
- Template variables for dynamic content generation
- Validation rules for required fields
- Output configuration for docs/devJournal/ directory
- Consistent with other YAML templates in framework
Updated References:
- dev.md agent updated to use dev-journal-tmpl.yaml
- create-dev-journal.md task updated to reference YAML template
This completes the conversion of all framework templates to YAML format,
ensuring consistency and leveraging the full BMAD template system capabilities.
Consolidated duplicate project brief templates into a unified solution that supports
multiple workflow modes, and moved all Memory Bank templates to base templates folder.
Template Consolidation:
- Merged project-brief-tmpl.yaml and projectbrief-tmpl.yaml into unified template
- Created mode-based template supporting 3 workflows:
* Comprehensive Mode: Full product development brief with elicitation
* Memory Bank Mode: Foundation document for Memory Bank system
* Rapid Mode: Quick project documentation with structured prompts
- Maintains backward compatibility while eliminating duplication
Template Organization:
- Moved all Memory Bank templates from memory-bank/ to base templates/ folder
- Updated all agents to include Memory Bank templates in dependencies
- Simplified template structure and references across framework
Updated Components:
- architect.md: Added all Memory Bank templates to dependencies
- dev.md: Added activeContext and progress templates
- po.md: Added relevant Memory Bank templates for requirements management
- initialize-memory-bank.md: Updated template references and added usage notes
Benefits:
- Single source of truth for project brief creation
- Flexible workflow support for different use cases
- Simplified template management and discovery
- Consistent framework organization
- Better integration between standalone and Memory Bank workflows
Converted all Memory Bank templates and ADR template from Markdown to YAML format
for consistency with BMAD framework template standards.
Template Conversions:
- projectbrief-tmpl.md → projectbrief-tmpl.yaml
- productContext-tmpl.md → productContext-tmpl.yaml
- systemPatterns-tmpl.md → systemPatterns-tmpl.yaml
- techContext-tmpl.md → techContext-tmpl.yaml
- activeContext-tmpl.md → activeContext-tmpl.yaml
- progress-tmpl.md → progress-tmpl.yaml
- adr-tmpl.md → adr-tmpl.yaml
YAML Template Features:
- Structured workflow definitions with guided/interactive modes
- Comprehensive prompting system for elicitation
- Section-based organization with clear instructions
- Output format configuration (markdown files in docs/memory-bank/)
- Validation rules for required fields
- Template variable system with Handlebars-style syntax
Updated References:
- initialize-memory-bank.md task updated to reference YAML templates
- create-adr.md task updated to reference YAML ADR template
- architect.md agent updated to use adr-tmpl.yaml
This maintains the same output structure while providing the structured,
interactive template experience consistent with other BMAD framework templates.
Implemented Cline-inspired Memory Bank pattern for AI context persistence across sessions.
This ensures continuity and deep understanding of projects even when AI memory resets.
Core Memory Bank Components:
- Created 6 core memory bank templates following hierarchical structure
- projectbrief.md: Foundation document with project scope and goals
- productContext.md: The 'why' behind the project
- systemPatterns.md: Technical architecture and decisions
- techContext.md: Technology stack and environment
- activeContext.md: Current work focus and priorities
- progress.md: Project state tracking and evolution
Tasks and Workflows:
- initialize-memory-bank.md: Creates initial Memory Bank structure
- update-memory-bank.md: Updates based on dev journals, ADRs, and changes
- memory-bank-triggers.md: Reference guide for when to update
Agent Integrations:
- Enhanced architect agent with Memory Bank awareness and commands
- Enhanced dev agent to update activeContext and progress
- Enhanced po agent for requirements alignment with Memory Bank
- All agents now read Memory Bank at session start
Pervasive Integration Strategy:
- ADR creation triggers systemPatterns updates
- Dev journal entries trigger activeContext updates
- Story completion triggers progress updates
- Comprehensive commits/PRs trigger relevant updates
- Document-project task integrates with Memory Bank initialization
This provides AI agents with persistent context across sessions, preventing
loss of project knowledge and ensuring consistent understanding.
- Created create-comprehensive-commit.md task with anti-tunnel vision mechanisms
- Multi-stream aware commit message generation
- Systematic evidence gathering from multiple sources
- Comprehensive context analysis and rationale documentation
- Quality checklist to prevent tunnel vision
- Created create-comprehensive-pr.md task for detailed PR descriptions
- Work stream identification and documentation
- Per-stream testing instructions
- Visual evidence requirements
- Review focus areas and deployment notes
- Integrated workflows into dev and architect agents
- Added *comprehensive-commit command
- Added *comprehensive-pr command
- Made workflows available to agents who create commits/PRs
These workflows ensure high-quality git documentation with comprehensive
coverage of all changes, preventing the tunnel vision that often results
in incomplete commit messages or PR descriptions.
- Removed unnecessary folders from BMAD-METHOD repo (docs/adr, docs/devJournal)
- Updated tasks to create folders in destination projects when needed
- Removed standalone adr-specialist agent (functionality integrated into architect)
- Added create-adr task with folder setup instructions
- Both ADR and Dev Journal features now properly create their structures in target projects
The agents will now create and maintain docs/adr and docs/devJournal folders
in the projects where BMAD is installed, not in the BMAD-METHOD repo itself.
- Created comprehensive ADR template following Michael Nygard's format
- Enhanced architect agent with ADR management capabilities
- Added ADR triggers reference guide for decision documentation
- Updated architect checklist with ADR validation section
- Imported user's comprehensive development methodology in tmp/
- Memory Bank system for AI context persistence
- Detailed rules covering coding principles and architecture patterns
- Workflows for common development tasks with anti-tunnel vision checks
- Created foundation for integrating user methodology with BMAD
- Fixed pre-commit hook by removing non-existent test script
This enhancement brings structured architectural decision documentation
to BMAD while preparing for deeper integration with advanced AI-assisted
development patterns.
* Added 1.0 files
* Converted agents, and templates to new format. Updated filenames to include extensions like in unity-2d-game-team.yaml, Updated some wordage in workflow, config, and increased minor version number
* Forgot to remove unused startup section in game-sm since it's moved to activation-instructions, now fixed.
* Updated verbosity for development workflow in development-guidenlines.md
* built the web-dist files for the expansion pack
* Synched with main repo and rebuilt dist
* Added enforcement of game-design-checklist to designer persona
* Updated with new changes to phaser epack that seem relevant to discussion we had on discord for summarizing documentation updates
* updated dist build for our epack
* refactor: simplify installer package version sync script and add comments
* chore: bump core version based on provided semver type
* chore(expansion): bump bmad-creator-tools version (patch)
Lucas C
semantic-release-bot
Brian Madison
A. R.
PinkyD
Jorge Castillo
MIPAN
Zach
Hossam Ghanam