Implement comprehensive DevOps integration supporting both GitHub Issues and
Azure DevOps across the full BMM workflow lifecycle.
## New Features
### Sprint Planning (sprint-planning)
- Create GitHub milestones or Azure DevOps iterations for sprint tracking
- Create epic-level issues/work items with proper labels/tags
- Store tracking references in sprint-status.yaml
### Story Creation (create-story)
- Link stories to milestones/iterations when creating tracking items
- Establish parent-child relationships between epics and stories
- Support GitHub milestone assignment and Azure DevOps iteration paths
### Story Implementation (dev-story)
- Auto-link PRs to issues using 'Closes #X' syntax for GitHub
- Link PRs to work items using --work-items flag for Azure DevOps
- Provider-aware branch naming convention (story/{{story_key}})
### Code Review (code-review)
- Post review comments to GitHub issues or Azure DevOps work items
- Provider-aware PR merge with squash strategy
- Automatic issue/work item closure on merge
### Correct Course (correct-course)
- Sync mid-sprint changes to external tracking systems
- Create/update/remove tracking items based on change proposals
- Support add, modify, and descope operations
### Retrospective (retrospective)
- Create retrospective issues/work items with action items
- Auto-close epic issues/work items when all stories complete
- Link retrospective records to parent epic
### Configuration & Documentation
- New devops-providers.yaml with CLI command reference for both providers
- Enhanced sprint-status-template.yaml with provider configuration docs
- Support for file-system, github-issues, and azure-devops tracking systems
## Files Changed
- src/modules/bmm/data/devops-providers.yaml (new)
- src/modules/bmm/workflows/4-implementation/sprint-planning/instructions.md
- src/modules/bmm/workflows/4-- Post review comment-planning/sprint-status-template.yaml
- src/modules/bmm/workflows/4-implementation/create-story/instructions.xml
- src/modules/bmm/workflows/4-implementation/dev-story/instructions.xml
- src/modules/bmm/workflows/4-implementation/code-review/instructions.xml
- src/modules/bmm/workflows/4-implementation/correct-course/instructions.md
- src/modules/bmm/workflows/4-implementation/retrospective/instructions.md
- Fix XML syntax error in dev-story/instructions.xml:20 (goto element)
- Fix path typo in tech-writer.agent.yaml (_bmadbmm → _bmad/bmm)
- Fix wrong route in analyst.agent.yaml (edit-agent → party-mode)
- Comment out unimplemented validate-create-story in sm.agent.yaml
- Comment out unimplemented validate-design in ux-designer.agent.yaml
- Remove misleading validate-create-story reference in create-story output
Fixes#1075
Related to #1163🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
Co-authored-by: Brian <bmadcode@gmail.com>
The `drafted` story state is no longer used since create-story now sets
status directly to `ready-for-dev`. This PR removes all references to
this legacy state from BMM documentation and workflow files.
Changes:
- Remove `drafted` from story status definitions and state machine docs
- Remove dead story-context file detection (story-context files no longer exist)
- Replace "draft" verb with "create" in story-related messaging
- Add legacy `drafted` → `ready-for-dev` migration in sprint-status
- Clarify that validate-create-story is optional and doesn't change status
- Document story handoff sequence: create-story → (optional) validate → dev-story
Story lifecycle is now: backlog → ready-for-dev → in-progress → review → done
Closes#1089🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
MAJOR BREAKING CHANGES: Phase 4 completely reengineered for developer efficiency and quality
🚀 **Phase 4 Streamlined & Supercharged:**
- **Reduced from 11 to 5 essential workflows** (55% reduction in complexity)
- **Eliminated redundant steps** that created token waste and confusion
- **Created single source of truth** story files with comprehensive implementation context
- **Achieved more reliable results** with fewer steps and better developer guidance
💡 **Revolutionary Dev Agent Behavior Fixes:**
- **Story file is now LAW:** Tasks/subtasks sequence is absolutely binding
- **Red-green-refactor enforcement:** Tests written first, validated, then implementation
- **Zero tolerance for cheating:** Tests must ACTUALLY exist and pass before marking complete
- **Sequential execution only:** No more "doing whatever you want" - follow the story exactly
- **Continuous execution:** No premature pausing until all tasks complete
🎯 **Quality Competition System:**
- **Enhanced story context engine** prevents common LLM development mistakes
- **Quality competition between LLMs** ensures optimal story preparation
- **Comprehensive anti-pattern prevention** stops wheel reinvention and wrong approaches
- **Developer optimization focus** for maximum clarity with minimum verbosity
📋 **Enhanced Definition of Done:**
- **27-point validation checklist** covers all implementation aspects
- **Multiple validation gates** prevent claiming work that isn't actually done
- **Comprehensive test requirements** ensure no functionality goes untested
- **File tracking and documentation** for complete project visibility
🔧 **Technical Improvements:**
- **Variable consistency** throughout all workflow files
- **XML instruction format** for better workflow engine compatibility
- **Proper ask tag handling** for user interaction clarity
- **Project context integration** without blocking implementation
- **Fixed all agent schema compliance** for proper array formatting
**Result:** Phase 4 now delivers superior development outcomes with:
- ✅ **55% fewer workflows** to learn and maintain
- ✅ **Dramatically reduced token usage** and context switching
- ✅ **Eliminated dev agent behavioral issues** that caused quality problems
- ✅ **Faster time-to-completion** with more reliable, predictable results
- ✅ **Better developer experience** with clearer guidance and validation
This represents the most significant Phase 4 improvement since BMAD Method inception - fundamentally fixing developer workflow quality while drastically simplifying the implementation process.
Sjoerd Bozon
Serhii
Brian Madison
Alex Verkhovsky