mirror of https://github.com/bmadcode/BMAD-METHOD.git synced 2025-12-29 16:14:59 +00:00

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

1.2 KiB

Raw Blame History

{{project_name}} - Epic Breakdown

Date: {{date}} Project Level: {{project_level}}

Epic {{N}}: {{epic_title_N}}

Slug: {{epic_slug_N}}

Goal

Scope

Success Criteria

Dependencies

Story Map - Epic {{N}}

Stories - 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}}

Estimated Effort: {{story_points}} points ({{time_estimate}})

Implementation Timeline - Epic {{N}}

Total Story Points: {{total_points_N}}

Estimated Timeline: {{estimated_timeline_N}}

Tech-Spec Reference

See tech-spec.md for complete technical implementation details.

1.2 KiB Raw Blame History