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.
77 lines
971 B
Markdown
77 lines
971 B
Markdown
# Epic Technical Specification: {{epic_title}}
|
|
|
|
Date: {{date}}
|
|
Author: {{user_name}}
|
|
Epic ID: {{epic_id}}
|
|
Status: Draft
|
|
|
|
---
|
|
|
|
## Overview
|
|
|
|
{{overview}}
|
|
|
|
## Objectives and Scope
|
|
|
|
{{objectives_scope}}
|
|
|
|
## System Architecture Alignment
|
|
|
|
{{system_arch_alignment}}
|
|
|
|
## Detailed Design
|
|
|
|
### Services and Modules
|
|
|
|
{{services_modules}}
|
|
|
|
### Data Models and Contracts
|
|
|
|
{{data_models}}
|
|
|
|
### APIs and Interfaces
|
|
|
|
{{apis_interfaces}}
|
|
|
|
### Workflows and Sequencing
|
|
|
|
{{workflows_sequencing}}
|
|
|
|
## Non-Functional Requirements
|
|
|
|
### Performance
|
|
|
|
{{nfr_performance}}
|
|
|
|
### Security
|
|
|
|
{{nfr_security}}
|
|
|
|
### Reliability/Availability
|
|
|
|
{{nfr_reliability}}
|
|
|
|
### Observability
|
|
|
|
{{nfr_observability}}
|
|
|
|
## Dependencies and Integrations
|
|
|
|
{{dependencies_integrations}}
|
|
|
|
## Acceptance Criteria (Authoritative)
|
|
|
|
{{acceptance_criteria}}
|
|
|
|
## Traceability Mapping
|
|
|
|
{{traceability_mapping}}
|
|
|
|
## Risks, Assumptions, Open Questions
|
|
|
|
{{risks_assumptions_questions}}
|
|
|
|
## Test Strategy Summary
|
|
|
|
{{test_strategy}}
|