- 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.
3.3 KiB
{{project_name}} - Product Requirements Document
Author: {{user_name}} Date: {{date}} Version: 1.0
Executive Summary
{{vision_alignment}}
What Makes This Special
{{product_magic_essence}}
Project Classification
Technical Type: {{project_type}} Domain: {{domain_type}} Complexity: {{complexity_level}}
{{project_classification}}
{{#if domain_context_summary}}
Domain Context
{{domain_context_summary}} {{/if}}
Success Criteria
{{success_criteria}}
{{#if business_metrics}}
Business Metrics
{{business_metrics}} {{/if}}
Product Scope
MVP - Minimum Viable Product
{{mvp_scope}}
Growth Features (Post-MVP)
{{growth_features}}
Vision (Future)
{{vision_features}}
{{#if domain_considerations}}
Domain-Specific Requirements
{{domain_considerations}}
This section shapes all functional and non-functional requirements below. {{/if}}
{{#if innovation_patterns}}
Innovation & Novel Patterns
{{innovation_patterns}}
Validation Approach
{{validation_approach}} {{/if}}
{{#if project_type_requirements}}
{{project_type}} Specific Requirements
{{project_type_requirements}}
{{#if endpoint_specification}}
API Specification
{{endpoint_specification}} {{/if}}
{{#if authentication_model}}
Authentication & Authorization
{{authentication_model}} {{/if}}
{{#if platform_requirements}}
Platform Support
{{platform_requirements}} {{/if}}
{{#if device_features}}
Device Capabilities
{{device_features}} {{/if}}
{{#if tenant_model}}
Multi-Tenancy Architecture
{{tenant_model}} {{/if}}
{{#if permission_matrix}}
Permissions & Roles
{{permission_matrix}} {{/if}} {{/if}}
{{#if ux_principles}}
User Experience Principles
{{ux_principles}}
Key Interactions
{{key_interactions}} {{/if}}
Functional Requirements
{{functional_requirements_complete}}
Non-Functional Requirements
{{#if performance_requirements}}
Performance
{{performance_requirements}} {{/if}}
{{#if security_requirements}}
Security
{{security_requirements}} {{/if}}
{{#if scalability_requirements}}
Scalability
{{scalability_requirements}} {{/if}}
{{#if accessibility_requirements}}
Accessibility
{{accessibility_requirements}} {{/if}}
{{#if integration_requirements}}
Integration
{{integration_requirements}} {{/if}}
{{#if no_nfrs}} No specific non-functional requirements identified for this project type. {{/if}}
Implementation Planning
Epic Breakdown Required
Requirements must be decomposed into epics and bite-sized stories (200k context limit).
Next Step: Run workflow epics-stories to create the implementation breakdown.
References
{{#if product_brief_path}}
- Product Brief: {{product_brief_path}} {{/if}} {{#if domain_brief_path}}
- Domain Brief: {{domain_brief_path}} {{/if}} {{#if research_documents}}
- Research: {{research_documents}} {{/if}}
Next Steps
- Epic & Story Breakdown - Run:
workflow epics-stories - UX Design (if UI) - Run:
workflow ux-design - Architecture - Run:
workflow create-architecture
This PRD captures the essence of {{project_name}} - {{product_magic_summary}}
Created through collaborative discovery between {{user_name}} and AI facilitator.