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.
181 lines
2.5 KiB
Markdown
181 lines
2.5 KiB
Markdown
# Domain Brief - {project_name}
|
|
|
|
Generated: {date}
|
|
Domain: {primary_domain}
|
|
Complexity: {complexity_level}
|
|
|
|
## Executive Summary
|
|
|
|
{brief_overview_of_domain_research_findings}
|
|
|
|
## Domain Overview
|
|
|
|
### Industry Context
|
|
|
|
{domain_overview}
|
|
|
|
### Regulatory Landscape
|
|
|
|
{regulatory_environment}
|
|
|
|
### Key Stakeholders
|
|
|
|
{stakeholder_analysis}
|
|
|
|
## Critical Concerns
|
|
|
|
### Compliance Requirements
|
|
|
|
{concern_mapping}
|
|
|
|
### Technical Constraints
|
|
|
|
{technical_limitations_from_domain}
|
|
|
|
### Safety/Risk Considerations
|
|
|
|
{safety_risk_factors}
|
|
|
|
## Regulatory Requirements
|
|
|
|
{regulatory_requirements}
|
|
|
|
## Industry Standards
|
|
|
|
{industry_standards}
|
|
|
|
## Practical Implications
|
|
|
|
### Architecture Impact
|
|
|
|
{architecture_implications}
|
|
|
|
### Development Impact
|
|
|
|
{development_implications}
|
|
|
|
### Timeline Impact
|
|
|
|
{timeline_implications}
|
|
|
|
### Cost Impact
|
|
|
|
{cost_implications}
|
|
|
|
## Domain Patterns
|
|
|
|
### Established Patterns
|
|
|
|
{domain_patterns}
|
|
|
|
### Innovation Opportunities
|
|
|
|
{innovation_notes}
|
|
|
|
## Risk Assessment
|
|
|
|
### Identified Risks
|
|
|
|
{risk_assessment}
|
|
|
|
### Mitigation Strategies
|
|
|
|
{mitigation_approaches}
|
|
|
|
## Validation Strategy
|
|
|
|
### Compliance Validation
|
|
|
|
{compliance_validation_approach}
|
|
|
|
### Technical Validation
|
|
|
|
{technical_validation_approach}
|
|
|
|
### Domain Expert Validation
|
|
|
|
{expert_validation_approach}
|
|
|
|
## Key Decisions
|
|
|
|
{key_decisions}
|
|
|
|
## Recommendations
|
|
|
|
### Must Have (Critical)
|
|
|
|
{critical_requirements}
|
|
|
|
### Should Have (Important)
|
|
|
|
{important_requirements}
|
|
|
|
### Consider (Nice-to-Have)
|
|
|
|
{optional_enhancements}
|
|
|
|
### Development Sequence
|
|
|
|
{recommended_sequence}
|
|
|
|
### Required Expertise
|
|
|
|
{expertise_needed}
|
|
|
|
## PRD Integration Guide
|
|
|
|
### Summary for PRD
|
|
|
|
{summary_for_prd}
|
|
|
|
### Requirements to Incorporate
|
|
|
|
- {requirement_1}
|
|
- {requirement_2}
|
|
- {requirement_3}
|
|
|
|
### Architecture Considerations
|
|
|
|
- {architecture_consideration_1}
|
|
- {architecture_consideration_2}
|
|
|
|
### Development Considerations
|
|
|
|
- {development_consideration_1}
|
|
- {development_consideration_2}
|
|
|
|
## References
|
|
|
|
### Regulations Researched
|
|
|
|
- {regulation_1_with_link}
|
|
- {regulation_2_with_link}
|
|
|
|
### Standards Referenced
|
|
|
|
- {standard_1_with_link}
|
|
- {standard_2_with_link}
|
|
|
|
### Additional Resources
|
|
|
|
- {resource_1}
|
|
- {resource_2}
|
|
|
|
## Appendix
|
|
|
|
### Research Notes
|
|
|
|
{detailed_research_notes}
|
|
|
|
### Conversation Highlights
|
|
|
|
{key_discussion_points_with_user}
|
|
|
|
### Open Questions
|
|
|
|
{questions_requiring_further_research}
|
|
|
|
---
|
|
|
|
_This domain brief was created through collaborative research between {user_name} and the AI facilitator. It should be referenced during PRD creation and updated as new domain insights emerge._
|