mirror of
https://github.com/bmadcode/BMAD-METHOD.git
synced 2025-12-29 16:14:59 +00:00
cfedecbd53
## 📚 Complete Documentation Restructure **BMM Documentation Hub Created:** - New centralized documentation system at `src/modules/bmm/docs/` - 18 comprehensive guides organized by topic (7000+ lines total) - Clear learning paths for greenfield, brownfield, and quick spec flows - Professional technical writing standards throughout **New Documentation:** - `README.md` - Complete documentation hub with navigation - `quick-start.md` - 15-minute getting started guide - `agents-guide.md` - Comprehensive 12-agent reference (45 min read) - `party-mode.md` - Multi-agent collaboration guide (20 min read) - `scale-adaptive-system.md` - Deep dive on Levels 0-4 (42 min read) - `brownfield-guide.md` - Existing codebase development (53 min read) - `quick-spec-flow.md` - Rapid Level 0-1 development (26 min read) - `workflows-analysis.md` - Phase 1 workflows (12 min read) - `workflows-planning.md` - Phase 2 workflows (19 min read) - `workflows-solutioning.md` - Phase 3 workflows (13 min read) - `workflows-implementation.md` - Phase 4 workflows (33 min read) - `workflows-testing.md` - Testing & QA workflows (29 min read) - `workflow-architecture-reference.md` - Architecture workflow deep-dive - `workflow-document-project-reference.md` - Document-project workflow reference - `enterprise-agentic-development.md` - Team collaboration patterns - `faq.md` - Comprehensive Q&A covering all topics - `glossary.md` - Complete terminology reference - `troubleshooting.md` - Common issues and solutions **Documentation Improvements:** - Removed all version/date footers (git handles versioning) - Agent customization docs now include full rebuild process - Cross-referenced links between all guides - Reading time estimates for all major docs - Consistent professional formatting and structure **Consolidated & Streamlined:** - Module README (`src/modules/bmm/README.md`) streamlined to lean signpost - Root README polished with better hierarchy and clear CTAs - Moved docs from root `docs/` to module-specific locations - Better separation of user docs vs. developer reference ## 🤖 New Agent: Paige (Documentation Guide) **Role:** Technical documentation specialist and information architect **Expertise:** - Professional technical writing standards - Documentation structure and organization - Information architecture and navigation - User-focused content design - Style guide enforcement **Status:** Work in progress - Paige will evolve as documentation needs grow **Integration:** - Listed in agents-guide.md, glossary.md, FAQ - Available for all phases (documentation is continuous) - Can be customized like all BMM agents ## 🔧 Additional Changes - Updated agent manifest with Paige - Updated workflow manifest with new documentation workflows - Fixed workflow-to-agent mappings across all guides - Improved root README with clearer Quick Start section - Better module structure explanations - Enhanced community links with Discord channel names **Total Impact:** - 18 new/restructured documentation files - 7000+ lines of professional technical documentation - Complete navigation system with cross-references - Clear learning paths for all user types - Foundation for knowledge base (coming in beta) Co-Authored-By: Claude <noreply@anthropic.com>
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_story_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
|