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.
60 lines
1.7 KiB
YAML
60 lines
1.7 KiB
YAML
# BMM Project Scale Levels - Source of Truth
|
|
# Reference: /.bmad/bmm/README.md lines 77-85
|
|
|
|
levels:
|
|
0:
|
|
name: "Level 0"
|
|
title: "Single Atomic Change"
|
|
stories: "1 story"
|
|
description: "Bug fix, tiny feature, one small change"
|
|
documentation: "Minimal - tech spec only"
|
|
architecture: false
|
|
|
|
1:
|
|
name: "Level 1"
|
|
title: "Small Feature"
|
|
stories: "1-10 stories"
|
|
description: "Small coherent feature, minimal documentation"
|
|
documentation: "Tech spec"
|
|
architecture: false
|
|
|
|
2:
|
|
name: "Level 2"
|
|
title: "Medium Project"
|
|
stories: "5-15 stories"
|
|
description: "Multiple features, focused PRD"
|
|
documentation: "PRD + optional tech spec"
|
|
architecture: false
|
|
|
|
3:
|
|
name: "Level 3"
|
|
title: "Complex System"
|
|
stories: "12-40 stories"
|
|
description: "Subsystems, integrations, full architecture"
|
|
documentation: "PRD + architecture + JIT tech specs"
|
|
architecture: true
|
|
|
|
4:
|
|
name: "Level 4"
|
|
title: "Enterprise Scale"
|
|
stories: "40+ stories"
|
|
description: "Multiple products, enterprise architecture"
|
|
documentation: "PRD + architecture + JIT tech specs"
|
|
architecture: true
|
|
|
|
# Quick detection hints for workflow-init
|
|
detection_hints:
|
|
keywords:
|
|
level_0: ["fix", "bug", "typo", "small change", "quick update", "patch"]
|
|
level_1: ["simple", "basic", "small feature", "add", "minor"]
|
|
level_2: ["dashboard", "several features", "admin panel", "medium"]
|
|
level_3: ["platform", "integration", "complex", "system", "architecture"]
|
|
level_4: ["enterprise", "multi-tenant", "multiple products", "ecosystem", "scale"]
|
|
|
|
story_counts:
|
|
level_0: [1, 1]
|
|
level_1: [1, 10]
|
|
level_2: [5, 15]
|
|
level_3: [12, 40]
|
|
level_4: [40, 999]
|