mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
7eb52520fa
- 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.
72 lines
2.8 KiB
YAML
72 lines
2.8 KiB
YAML
# Retrospective - Epic Completion Review Workflow
|
|
name: "retrospective"
|
|
description: "Run after epic completion to review overall success, extract lessons learned, and explore if new information emerged that might impact the next epic"
|
|
author: "BMad"
|
|
|
|
config_source: "{project-root}/.bmad/bmm/config.yaml"
|
|
output_folder: "{config_source}:output_folder"
|
|
user_name: "{config_source}:user_name"
|
|
communication_language: "{config_source}:communication_language"
|
|
user_skill_level: "{config_source}:user_skill_level"
|
|
document_output_language: "{config_source}:document_output_language"
|
|
date: system-generated
|
|
|
|
installed_path: "{project-root}/.bmad/bmm/workflows/4-implementation/retrospective"
|
|
template: false
|
|
instructions: "{installed_path}/instructions.md"
|
|
|
|
mode: interactive
|
|
trigger: "Run AFTER completing an epic"
|
|
|
|
required_inputs:
|
|
- agent_manifest: "{project-root}/.bmad/_cfg/agent-manifest.csv"
|
|
|
|
# Smart input file references - handles both whole docs and sharded docs
|
|
# Priority: Whole document first, then sharded version
|
|
# Strategy: SELECTIVE LOAD - only load the completed epic and relevant retrospectives
|
|
input_file_patterns:
|
|
epics:
|
|
whole: "{output_folder}/*epic*.md"
|
|
sharded_index: "{output_folder}/*epic*/index.md"
|
|
sharded_single: "{output_folder}/*epic*/epic-{{epic_num}}.md"
|
|
|
|
previous_retrospective:
|
|
pattern: "{output_folder}/retrospectives/epic-{{prev_epic_num}}-retro-*.md"
|
|
|
|
architecture:
|
|
whole: "{output_folder}/*architecture*.md"
|
|
sharded: "{output_folder}/*architecture*/index.md"
|
|
|
|
prd:
|
|
whole: "{output_folder}/*prd*.md"
|
|
sharded: "{output_folder}/*prd*/index.md"
|
|
|
|
document_project:
|
|
sharded: "{output_folder}/docs/index.md"
|
|
|
|
# Required files
|
|
sprint_status_file: "{output_folder}/sprint-status.yaml"
|
|
story_directory: "{config_source}:dev_ephemeral_location"
|
|
retrospectives_folder: "{output_folder}/retrospectives"
|
|
|
|
output_artifacts:
|
|
- retrospective_summary: "Comprehensive review of what went well and what could improve"
|
|
- lessons_learned: "Key insights for future epics"
|
|
- action_items: "Specific improvements with ownership"
|
|
- next_epic_preparation: "Dependencies, gaps, and preparation tasks for next epic"
|
|
- critical_path: "Blockers or prerequisites that must be addressed"
|
|
|
|
facilitation:
|
|
facilitator: "Bob (Scrum Master)"
|
|
tone: "Psychological safety - no blame, focus on systems and processes"
|
|
format: "Two-part: (1) Review completed epic + (2) Preview next epic preparation"
|
|
|
|
validation_required:
|
|
- testing_complete: "Has full regression testing been completed?"
|
|
- deployment_status: "Has epic been deployed to production?"
|
|
- business_validation: "Have stakeholders reviewed and accepted deliverables?"
|
|
- technical_health: "Is codebase in stable, maintainable state?"
|
|
- blocker_resolution: "Any unresolved blockers that will impact next epic?"
|
|
|
|
standalone: true
|