- 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.
2.0 KiB
{{project_name}} - Technical Specification
Author: {{user_name}} Date: {{date}} Project Level: {{project_level}} Change Type: {{change_type}} Development Context: {{development_context}}
Context
Available Documents
{{loaded_documents_summary}}
Project Stack
{{project_stack_summary}}
Existing Codebase Structure
{{existing_structure_summary}}
The Change
Problem Statement
{{problem_statement}}
Proposed Solution
{{solution_overview}}
Scope
In Scope:
{{scope_in}}
Out of Scope:
{{scope_out}}
Implementation Details
Source Tree Changes
{{source_tree_changes}}
Technical Approach
{{technical_approach}}
Existing Patterns to Follow
{{existing_patterns}}
Integration Points
{{integration_points}}
Development Context
Relevant Existing Code
{{existing_code_references}}
Dependencies
Framework/Libraries:
{{framework_dependencies}}
Internal Modules:
{{internal_dependencies}}
Configuration Changes
{{configuration_changes}}
Existing Conventions (Brownfield)
{{existing_conventions}}
Test Framework & Standards
{{test_framework_info}}
Implementation Stack
{{implementation_stack}}
Technical Details
{{technical_details}}
Development Setup
{{development_setup}}
Implementation Guide
Setup Steps
{{setup_steps}}
Implementation Steps
{{implementation_steps}}
Testing Strategy
{{testing_strategy}}
Acceptance Criteria
{{acceptance_criteria}}
Developer Resources
File Paths Reference
{{file_paths_complete}}
Key Code Locations
{{key_code_locations}}
Testing Locations
{{testing_locations}}
Documentation to Update
{{documentation_updates}}
UX/UI Considerations
{{ux_ui_considerations}}
Testing Approach
{{testing_approach}}
Deployment Strategy
Deployment Steps
{{deployment_steps}}
Rollback Plan
{{rollback_plan}}
Monitoring
{{monitoring_approach}}