mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
7eb52520fa
- Installation path is now fully configurable, allowing users to specify custom installation directories during setup
- Default installation location changed to .bmad (hidden directory) for cleaner project root organization
Web Bundle Improvements:
- All web bundles (single agent and team) now include party mode support for multi-agent collaboration!
- Advanced elicitation capabilities integrated into standalone agents
- All bundles enhanced with party mode agent manifests
- Added default-party.csv files to bmm, bmgd, and cis module teams
- The default party file is what will be used with single agent bundles. teams can customize for different party configurations before web bundling through a setting in the team yaml file
- New web bundle outputs for all agents (analyst, architect, dev, pm, sm, tea, tech-writer, ux-designer, game-*, creative-squad)
Phase 4 Workflow Updates (In Progress):
- Initiated shift to separate phase 4 implementation artifacts from documentation
- Phase 4 implementation artifacts (stories, code review, sprint plan, context files) will move to dedicated location outside docs folder
- Installer questions and configuration added for artifact path selection
- Updated workflow.yaml files for code-review, sprint-planning, story-context, epic-tech-context, and retrospective workflows to support this, but still might require some udpates
Additional Changes:
- New agent and action command header models for standardization
- Enhanced web-bundle-activation-steps fragment
- Updated web-bundler.js to support new structure
- VS Code settings updated for new .bmad directory
- Party mode instructions and workflow enhanced for better orchestration
IDE Installer Updates:
- Show version number of installer in cli
- improved Installer UX
- Gemini TOML Improved to have clear loading instructions with @ commands
- All tools agent launcher mds improved to use a central file template critical indication isntead of hardcoding in 2 different locations.
1.0 KiB
1.0 KiB
Senior Developer Review - Validation Checklist
- Story file loaded from
{{story_path}} - Story Status verified as one of: {{allow_status_values}}
- Epic and Story IDs resolved ({{epic_num}}.{{story_num}})
- Story Context located or warning recorded
- Epic Tech Spec located or warning recorded
- Architecture/standards docs loaded (as available)
- Tech stack detected and documented
- MCP doc search performed (or web fallback) and references captured
- Acceptance Criteria cross-checked against implementation
- File List reviewed and validated for completeness
- Tests identified and mapped to ACs; gaps noted
- Code quality review performed on changed files
- Security review performed on changed files and dependencies
- Outcome decided (Approve/Changes Requested/Blocked)
- Review notes appended under "Senior Developer Review (AI)"
- Change Log updated with review entry
- Status updated according to settings (if enabled)
- Story saved successfully
Reviewer: {{user_name}} on {{date}}