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.
2.1 KiB
2.1 KiB
Build Agent Validation Checklist (YAML Agents)
Agent Structure Validation
YAML Structure
- YAML parses without errors
agent.metadataincludes:id,name,title,icon,moduleagent.personaexists with role, identity, communication_style, and principlesagent.menuexists with at least one item
Core Components
metadata.idpoints to final compiled path:.bmad/{{module}}/agents/{{agent}}.mdmetadata.modulematches the module folder (e.g.,bmm,bmb,cis)- Principles are an array (preferred) or string with clear values
Persona Completeness
- Role clearly defines primary expertise area (1–2 lines)
- Identity includes relevant background and strengths (3–5 lines)
- Communication style gives concrete guidance (3–5 lines)
- Principles present and meaningful (no placeholders)
Menu Validation
- Triggers do not start with
*(auto-prefixed during build) - Each item has a
description - Handlers use valid attributes (
workflow,exec,tmpl,data,action) - Paths use
{project-root}or valid variables - No duplicate triggers
Optional Sections
promptsdefined when usingaction: "#id"critical_actionspresent if custom activation steps are needed- Customize file (if created) located at
{project-root}/.bmad/_cfg/agents/{{module}}-{{agent}}.customize.yaml
Build Verification
- Run compile to build
.md:npm run install:bmad→ "Compile Agents" (orbmad install→ Compile) - Confirm compiled file exists at
{project-root}/.bmad/{{module}}/agents/{{agent}}.md
Final Quality
- Filename is kebab-case and ends with
.agent.yaml - Output location correctly placed in module or standalone directory
- Agent purpose and commands are clear and consistent