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.
50 lines
1.5 KiB
YAML
50 lines
1.5 KiB
YAML
# Workflow Status Template
|
|
# This tracks progress through phases 1-3 of the BMM methodology
|
|
# Phase 4 (Implementation) is tracked separately in sprint-status.yaml
|
|
|
|
# generated: 2025-10-29
|
|
# project: Enterprise Customer Portal
|
|
# project_type: software
|
|
# project_level: 3
|
|
# field_type: greenfield
|
|
# workflow_path: greenfield-level-3.yaml
|
|
|
|
# STATUS DEFINITIONS:
|
|
# ==================
|
|
# Initial Status (before completion):
|
|
# - required: Must be completed to progress
|
|
# - optional: Can be completed but not required
|
|
# - recommended: Strongly suggested but not required
|
|
# - conditional: Required only if certain conditions met (e.g., if_has_ui)
|
|
#
|
|
# Completion Status:
|
|
# - {file-path}: File created/found (e.g., "docs/product-brief.md")
|
|
# - skipped: Optional/conditional workflow that was skipped
|
|
|
|
generated: 2025-10-29
|
|
project: Enterprise Customer Portal
|
|
project_type: software
|
|
project_level: 3
|
|
field_type: greenfield
|
|
workflow_path: greenfield-level-3.yaml
|
|
|
|
workflow_status:
|
|
# Phase 1: Analysis
|
|
brainstorm-project: docs/brainstorm-session-2025-10-15.md
|
|
research: docs/research-api-patterns.md
|
|
product-brief: docs/product-brief.md
|
|
|
|
# Phase 2: Planning
|
|
prd: docs/prd.md
|
|
validate-prd: skipped
|
|
create-design: docs/ux-design.md
|
|
|
|
# Phase 3: Solutioning
|
|
create-architecture: required
|
|
validate-architecture: optional
|
|
solutioning-gate-check: recommended
|
|
|
|
# Phase 4: Implementation
|
|
sprint-planning: required
|
|
# Note: Subsequent implementation workflows tracked in sprint-status.yaml
|