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.
33 lines
1.4 KiB
YAML
33 lines
1.4 KiB
YAML
# Convert Legacy - BMAD v4 to v6 Converter Configuration
|
|
name: "convert-legacy"
|
|
description: "Converts legacy BMAD v4 or similar items (agents, workflows, modules) to BMad Core compliant format with proper structure and conventions"
|
|
author: "BMad"
|
|
|
|
# Critical variables load from config_source
|
|
config_source: "{project-root}/.bmad/bmb/config.yaml"
|
|
output_folder: "{config_source}:output_folder"
|
|
user_name: "{config_source}:user_name"
|
|
communication_language: "{config_source}:communication_language"
|
|
date: system-generated
|
|
|
|
# Optional docs that can be provided as input
|
|
recommended_inputs:
|
|
- legacy_file: "Path to v4 agent, workflow, or module to convert"
|
|
|
|
# Module path and component files
|
|
installed_path: "{project-root}/.bmad/bmb/workflows/convert-legacy"
|
|
template: false # This is an action/meta workflow - no template needed
|
|
instructions: "{installed_path}/instructions.md"
|
|
validation: "{installed_path}/checklist.md"
|
|
|
|
# Output configuration - Creates converted items in appropriate module locations
|
|
default_output_folder: "{project-root}/.bmad/{{target_module}}/{{item_type}}/{{item_name}}"
|
|
|
|
# Sub-workflows that may be invoked for conversion
|
|
sub_workflows:
|
|
- create_agent: "{project-root}/.bmad/bmb/workflows/create-agent/workflow.yaml"
|
|
- create_workflow: "{project-root}/.bmad/bmb/workflows/create-workflow/workflow.yaml"
|
|
- create_module: "{project-root}/.bmad/bmb/workflows/create-module/workflow.yaml"
|
|
|
|
standalone: true
|