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

2.3 KiB

Product Brief: {{project_name}}

Date: {{date}} Author: {{user_name}} Context: {{context_type}}


Executive Summary

{{executive_summary}}


Core Vision

Problem Statement

{{problem_statement}}

{{#if problem_impact}}

Problem Impact

{{problem_impact}} {{/if}}

{{#if existing_solutions_gaps}}

Why Existing Solutions Fall Short

{{existing_solutions_gaps}} {{/if}}

Proposed Solution

{{proposed_solution}}

{{#if key_differentiators}}

Key Differentiators

{{key_differentiators}} {{/if}}


Target Users

Primary Users

{{primary_user_segment}}

{{#if secondary_user_segment}}

Secondary Users

{{secondary_user_segment}} {{/if}}

{{#if user_journey}}

User Journey

{{user_journey}} {{/if}}


{{#if success_metrics}}

Success Metrics

{{success_metrics}}

{{#if business_objectives}}

Business Objectives

{{business_objectives}} {{/if}}

{{#if key_performance_indicators}}

Key Performance Indicators

{{key_performance_indicators}} {{/if}} {{/if}}


MVP Scope

Core Features

{{core_features}}

{{#if out_of_scope}}

Out of Scope for MVP

{{out_of_scope}} {{/if}}

{{#if mvp_success_criteria}}

MVP Success Criteria

{{mvp_success_criteria}} {{/if}}

{{#if future_vision_features}}

Future Vision

{{future_vision_features}} {{/if}}


{{#if market_analysis}}

Market Context

{{market_analysis}} {{/if}}

{{#if financial_considerations}}

Financial Considerations

{{financial_considerations}} {{/if}}

{{#if technical_preferences}}

Technical Preferences

{{technical_preferences}} {{/if}}

{{#if organizational_context}}

Organizational Context

{{organizational_context}} {{/if}}

{{#if risks_and_assumptions}}

Risks and Assumptions

{{risks_and_assumptions}} {{/if}}

{{#if timeline_constraints}}

Timeline

{{timeline_constraints}} {{/if}}

{{#if supporting_materials}}

Supporting Materials

{{supporting_materials}} {{/if}}


This Product Brief captures the vision and requirements for {{project_name}}.

It was created through collaborative discovery and reflects the unique needs of this {{context_type}} project.

{{#if next_workflow}} Next: {{next_workflow}} will transform this brief into detailed planning artifacts. {{else}} Next: Use the PRD workflow to create detailed product requirements from this brief. {{/if}}