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.

.bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/epics-template.md

@@ -0,0 +1,52 @@
+# {{project_name}} - Epic Breakdown
+
+**Author:** {{user_name}}
+**Date:** {{date}}
+**Project Level:** {{project_level}}
+**Target Scale:** {{target_scale}}
+
+---
+
+## Overview
+
+This document provides the complete epic and story breakdown for {{project_name}}, decomposing the requirements from the [PRD](./PRD.md) into implementable stories.
+
+{{epics_summary}}
+
+---
+
+<!-- Repeat for each epic (N = 1, 2, 3...) -->
+
+## Epic {{N}}: {{epic_title_N}}
+
+{{epic_goal_N}}
+
+<!-- Repeat for each story (M = 1, 2, 3...) within epic N -->
+
+### Story {{N}}.{{M}}: {{story_title_N_M}}
+
+As a {{user_type}},
+I want {{capability}},
+So that {{value_benefit}}.
+
+**Acceptance Criteria:**
+
+**Given** {{precondition}}
+**When** {{action}}
+**Then** {{expected_outcome}}
+
+**And** {{additional_criteria}}
+
+**Prerequisites:** {{dependencies_on_previous_stories}}
+
+**Technical Notes:** {{implementation_guidance}}
+
+<!-- End story repeat -->
+
+---
+
+<!-- End epic repeat -->
+
+---
+
+_For implementation: Use the `create-story` workflow to generate individual story implementation plans from this epic breakdown._

.bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/instructions.md

@@ -0,0 +1,169 @@
+# Epic and Story Decomposition - Intent-Based Implementation Planning
+
+<critical>The workflow execution engine is governed by: {project-root}/.bmad/core/tasks/workflow.xml</critical>
+<critical>You MUST have already loaded and processed: {installed_path}/workflow.yaml</critical>
+<critical>This workflow transforms requirements into BITE-SIZED STORIES for development agents</critical>
+<critical>EVERY story must be completable by a single dev agent in one focused session</critical>
+<critical>Communicate all responses in {communication_language} and adapt to {user_skill_level}</critical>
+<critical>Generate all documents in {document_output_language}</critical>
+<critical>LIVING DOCUMENT: Write to epics.md continuously as you work - never wait until the end</critical>
+<critical>Input documents specified in workflow.yaml input_file_patterns - workflow engine handles fuzzy matching, whole vs sharded document discovery automatically</critical>
+
+<workflow>
+
+<step n="1" goal="Load PRD and extract requirements">
+<action>Welcome {user_name} to epic and story planning
+
+Load required documents (fuzzy match, handle both whole and sharded):
+
+- PRD.md (required)
+- domain-brief.md (if exists)
+- product-brief.md (if exists)
+
+Extract from PRD:
+
+- All functional requirements
+- Non-functional requirements
+- Domain considerations and compliance needs
+- Project type and complexity
+- MVP vs growth vs vision scope boundaries
+
+Understand the context:
+
+- What makes this product special (the magic)
+- Technical constraints
+- User types and their goals
+- Success criteria</action>
+  </step>
+
+<step n="2" goal="Propose epic structure from natural groupings">
+<action>Analyze requirements and identify natural epic boundaries
+
+INTENT: Find organic groupings that make sense for THIS product
+
+Look for natural patterns:
+
+- Features that work together cohesively
+- User journeys that connect
+- Business capabilities that cluster
+- Domain requirements that relate (compliance, validation, security)
+- Technical systems that should be built together
+
+Name epics based on VALUE, not technical layers:
+
+- Good: "User Onboarding", "Content Discovery", "Compliance Framework"
+- Avoid: "Database Layer", "API Endpoints", "Frontend"
+
+Each epic should:
+
+- Have clear business goal and user value
+- Be independently valuable
+- Contain 3-8 related capabilities
+- Be deliverable in cohesive phase
+
+For greenfield projects:
+
+- First epic MUST establish foundation (project setup, core infrastructure, deployment pipeline)
+- Foundation enables all subsequent work
+
+For complex domains:
+
+- Consider dedicated compliance/regulatory epics
+- Group validation and safety requirements logically
+- Note expertise requirements
+
+Present proposed epic structure showing:
+
+- Epic titles with clear value statements
+- High-level scope of each epic
+- Suggested sequencing
+- Why this grouping makes sense</action>
+
+<template-output>epics_summary</template-output>
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
+</step>
+
+<step n="3" goal="Decompose each epic into bite-sized stories" repeat="for-each-epic">
+<action>Break down Epic {{N}} into small, implementable stories
+
+INTENT: Create stories sized for single dev agent completion
+
+For each epic, generate:
+
+- Epic title as `epic_title_{{N}}`
+- Epic goal/value as `epic_goal_{{N}}`
+- All stories as repeated pattern `story_title_{{N}}_{{M}}` for each story M
+
+CRITICAL for Epic 1 (Foundation):
+
+- Story 1.1 MUST be project setup/infrastructure initialization
+- Sets up: repo structure, build system, deployment pipeline basics, core dependencies
+- Creates foundation for all subsequent stories
+- Note: Architecture workflow will flesh out technical details
+
+Each story should follow BDD-style acceptance criteria:
+
+**Story Pattern:**
+As a [user type],
+I want [specific capability],
+So that [clear value/benefit].
+
+**Acceptance Criteria using BDD:**
+Given [precondition or initial state]
+When [action or trigger]
+Then [expected outcome]
+
+And [additional criteria as needed]
+
+**Prerequisites:** Only previous stories (never forward dependencies)
+
+**Technical Notes:** Implementation guidance, affected components, compliance requirements
+
+Ensure stories are:
+
+- Vertically sliced (deliver complete functionality, not just one layer)
+- Sequentially ordered (logical progression, no forward dependencies)
+- Independently valuable when possible
+- Small enough for single-session completion
+- Clear enough for autonomous implementation
+
+For each story in epic {{N}}, output variables following this pattern:
+
+- story*title*{{N}}_1, story_title_{{N}}\_2, etc.
+- Each containing: user story, BDD acceptance criteria, prerequisites, technical notes</action>
+
+<template-output>epic*title*{{N}}</template-output>
+<template-output>epic*goal*{{N}}</template-output>
+
+<action>For each story M in epic {{N}}, generate story content</action>
+<template-output>story*title*{{N}}\_{{M}}</template-output>
+
+<invoke-task halt="true">{project-root}/.bmad/core/tasks/adv-elicit.xml</invoke-task>
+</step>
+
+<step n="4" goal="Review and finalize epic breakdown">
+<action>Review the complete epic breakdown for quality and completeness
+
+Validate:
+
+- All functional requirements from PRD are covered by stories
+- Epic 1 establishes proper foundation
+- All stories are vertically sliced
+- No forward dependencies exist
+- Story sizing is appropriate for single-session completion
+- BDD acceptance criteria are clear and testable
+- Domain/compliance requirements are properly distributed
+- Sequencing enables incremental value delivery
+
+Confirm with {user_name}:
+
+- Epic structure makes sense
+- Story breakdown is actionable
+- Dependencies are clear
+- BDD format provides clarity
+- Ready for architecture and implementation phases</action>
+
+<template-output>epic_breakdown_summary</template-output>
+</step>
+
+</workflow>

.bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories/workflow.yaml

@@ -0,0 +1,45 @@
+# Epic and Story Decomposition Workflow
+name: create-epics-and-stories
+description: "Transform PRD requirements into bite-sized stories organized in epics for 200k context dev agents"
+author: "BMad"
+
+# Critical variables from config
+config_source: "{project-root}/.bmad/bmm/config.yaml"
+project_name: "{config_source}:project_name"
+output_folder: "{config_source}:output_folder"
+user_name: "{config_source}:user_name"
+communication_language: "{config_source}:communication_language"
+document_output_language: "{config_source}:document_output_language"
+user_skill_level: "{config_source}:user_skill_level"
+date: system-generated
+
+# Input requirements
+recommended_inputs:
+  - prd: "Product Requirements Document with FRs and NFRs"
+  - product_brief: "Product Brief with vision and goals (optional)"
+  - domain_brief: "Domain-specific requirements and context (optional)"
+
+# Smart input file references - handles both whole docs and sharded docs
+# Priority: Whole document first, then sharded version
+input_file_patterns:
+  prd:
+    whole: "{output_folder}/*prd*.md"
+    sharded: "{output_folder}/*prd*/index.md"
+
+  product_brief:
+    whole: "{output_folder}/*product*brief*.md"
+    sharded: "{output_folder}/*product*brief*/index.md"
+
+  domain_brief:
+    whole: "{output_folder}/*domain*brief*.md"
+    sharded: "{output_folder}/*domain*brief*/index.md"
+
+# Module path and component files
+installed_path: "{project-root}/.bmad/bmm/workflows/2-plan-workflows/prd/create-epics-and-stories"
+instructions: "{installed_path}/instructions.md"
+template: "{installed_path}/epics-template.md"
+
+# Output configuration
+default_output_file: "{output_folder}/epics.md"
+
+standalone: true