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.
128 lines
4.1 KiB
YAML
128 lines
4.1 KiB
YAML
# BMad Enterprise Method - Brownfield
|
|
# Extended enterprise planning for complex brownfield with security/devops/test (30+ stories typically)
|
|
|
|
method_name: "BMad Enterprise Method"
|
|
track: "enterprise"
|
|
field_type: "brownfield"
|
|
description: "Enterprise-grade planning for complex brownfield additions with extended requirements"
|
|
|
|
phases:
|
|
- prerequisite: true
|
|
name: "Documentation"
|
|
conditional: "if_undocumented"
|
|
note: "NOT a phase - prerequisite for brownfield without docs (nearly mandatory for enterprise)"
|
|
workflows:
|
|
- id: "document-project"
|
|
required: true
|
|
agent: "analyst"
|
|
command: "document-project"
|
|
output: "Comprehensive project documentation"
|
|
purpose: "Understand existing codebase - critical for enterprise brownfield"
|
|
|
|
- phase: 0
|
|
name: "Discovery (Required)"
|
|
required: true
|
|
note: "Analysis phase required for enterprise projects"
|
|
workflows:
|
|
- id: "brainstorm-project"
|
|
optional: true
|
|
agent: "analyst"
|
|
command: "brainstorm-project"
|
|
included_by: "user_choice"
|
|
|
|
- id: "research"
|
|
recommended: true
|
|
agent: "analyst"
|
|
command: "research"
|
|
included_by: "user_choice"
|
|
note: "Highly recommended - compliance, integration, risk research"
|
|
|
|
- id: "product-brief"
|
|
optional: true
|
|
agent: "analyst"
|
|
command: "product-brief"
|
|
included_by: "user_choice"
|
|
note: "Optional for brownfield enterprise"
|
|
|
|
- phase: 1
|
|
name: "Planning"
|
|
required: true
|
|
workflows:
|
|
- id: "prd"
|
|
required: true
|
|
agent: "pm"
|
|
command: "prd"
|
|
output: "Enterprise PRD with compliance requirements"
|
|
note: "Must address existing system constraints and migration strategy"
|
|
|
|
- id: "validate-prd"
|
|
recommended: true
|
|
agent: "pm"
|
|
command: "validate-prd"
|
|
|
|
- id: "create-design"
|
|
recommended: true
|
|
agent: "ux-designer"
|
|
command: "create-design"
|
|
note: "Recommended - must integrate with existing UX patterns"
|
|
|
|
- id: "framework"
|
|
optional: true
|
|
agent: "tea"
|
|
command: "framework"
|
|
output: "Test framework scaffold (Playwright/Cypress)"
|
|
note: "Initialize or modernize test framework - critical if brownfield lacks proper test infrastructure"
|
|
|
|
- id: "ci"
|
|
optional: true
|
|
agent: "tea"
|
|
command: "ci"
|
|
output: "CI/CD test pipeline configuration"
|
|
note: "Establish or enhance CI pipeline with regression testing strategy"
|
|
|
|
- phase: 2
|
|
name: "Solutioning"
|
|
required: true
|
|
workflows:
|
|
- id: "create-architecture"
|
|
required: true
|
|
agent: "architect"
|
|
command: "create-architecture"
|
|
output: "Integration architecture with enterprise considerations"
|
|
note: "Distills brownfield context + adds security/scalability/compliance design"
|
|
|
|
- id: "create-security-architecture"
|
|
optional: true
|
|
agent: "architect"
|
|
command: "create-security-architecture"
|
|
output: "Security architecture for brownfield integration"
|
|
note: "Future workflow - optional extended enterprise workflow for threat model, auth integration, audit requirements"
|
|
|
|
- id: "create-devops-strategy"
|
|
optional: true
|
|
agent: "architect"
|
|
command: "create-devops-strategy"
|
|
output: "DevOps strategy for brownfield deployment"
|
|
note: "Future workflow - optional extended enterprise workflow for CI/CD integration, deployment strategy, monitoring"
|
|
|
|
- id: "validate-architecture"
|
|
optional: true
|
|
agent: "architect"
|
|
command: "validate-architecture"
|
|
|
|
- id: "solutioning-gate-check"
|
|
required: true
|
|
agent: "architect"
|
|
command: "solutioning-gate-check"
|
|
note: "Critical gate - validates all planning before touching production system"
|
|
|
|
- phase: 3
|
|
name: "Implementation"
|
|
required: true
|
|
workflows:
|
|
- id: "sprint-planning"
|
|
required: true
|
|
agent: "sm"
|
|
command: "sprint-planning"
|
|
note: "Enterprise brownfield requires careful phasing and feature flags"
|