Brian Madison 7eb52520fa Major Enhancements:
- 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.
2025-11-09 17:39:05 -06:00

276 lines
3.7 KiB
Markdown

# Module Brief: {{module_name}}
**Date:** {{date}}
**Author:** {{user_name}}
**Module Code:** {{module_code}}
**Status:** Ready for Development
---
## Executive Summary
{{module_vision}}
**Module Category:** {{module_category}}
**Complexity Level:** {{complexity_level}}
**Target Users:** {{target_users}}
---
## Module Identity
### Core Concept
{{module_identity}}
### Unique Value Proposition
What makes this module special:
{{unique_value}}
### Personality Theme
{{personality_theme}}
---
## Agent Architecture
{{agent_architecture}}
### Agent Roster
{{agent_roster}}
### Agent Interaction Model
How agents work together:
{{agent_interactions}}
---
## Workflow Ecosystem
{{workflow_ecosystem}}
### Core Workflows
Essential functionality that delivers primary value:
{{core_workflows}}
### Feature Workflows
Specialized capabilities that enhance the module:
{{feature_workflows}}
### Utility Workflows
Supporting operations and maintenance:
{{utility_workflows}}
---
## User Scenarios
### Primary Use Case
{{primary_scenario}}
### Secondary Use Cases
{{secondary_scenarios}}
### User Journey
Step-by-step walkthrough of typical usage:
{{user_journey}}
---
## Technical Planning
### Data Requirements
{{data_requirements}}
### Integration Points
{{integration_points}}
### Dependencies
{{dependencies}}
### Technical Complexity Assessment
{{technical_planning}}
---
## Success Metrics
### Module Success Criteria
How we'll know the module is successful:
{{success_criteria}}
### Quality Standards
{{quality_standards}}
### Performance Targets
{{performance_targets}}
---
## Development Roadmap
### Phase 1: MVP (Minimum Viable Module)
**Timeline:** {{phase1_timeline}}
{{phase1_components}}
**Deliverables:**
{{phase1_deliverables}}
### Phase 2: Enhancement
**Timeline:** {{phase2_timeline}}
{{phase2_components}}
**Deliverables:**
{{phase2_deliverables}}
### Phase 3: Polish and Optimization
**Timeline:** {{phase3_timeline}}
{{phase3_components}}
**Deliverables:**
{{phase3_deliverables}}
---
## Creative Features
### Special Touches
{{creative_features}}
### Easter Eggs and Delighters
{{easter_eggs}}
### Module Lore and Theming
{{module_lore}}
---
## Risk Assessment
### Technical Risks
{{technical_risks}}
### Usability Risks
{{usability_risks}}
### Scope Risks
{{scope_risks}}
### Mitigation Strategies
{{risk_mitigation}}
---
## Implementation Notes
### Priority Order
1. {{priority_1}}
2. {{priority_2}}
3. {{priority_3}}
### Key Design Decisions
{{design_decisions}}
### Open Questions
{{open_questions}}
---
## Resources and References
### Inspiration Sources
{{inspiration_sources}}
### Similar Modules
{{similar_modules}}
### Technical References
{{technical_references}}
---
## Appendices
### A. Detailed Agent Specifications
{{detailed_agent_specs}}
### B. Workflow Detailed Designs
{{detailed_workflow_specs}}
### C. Data Structures and Schemas
{{data_schemas}}
### D. Integration Specifications
{{integration_specs}}
---
## Next Steps
1. **Review this brief** with stakeholders
2. **Run create-module workflow** using this brief as input
3. **Create first agent** using create-agent workflow
4. **Develop initial workflows** using create-workflow
5. **Test MVP** with target users
---
_This Module Brief is ready to be fed directly into the create-module workflow for scaffolding and implementation._
**Module Viability Score:** {{viability_score}}/10
**Estimated Development Effort:** {{effort_estimate}}
**Confidence Level:** {{confidence_level}}
---
**Approval for Development:**
- [ ] Concept Approved
- [ ] Scope Defined
- [ ] Resources Available
- [ ] Ready to Build
---
_Generated on {{date}} by {{user_name}} using the BMAD Method Module Brief workflow_