Serhii
|
fa0115dfa3
|
fix(bmm): correct VCS config path in Architect/PM/Dev agents
ISSUE: Path Inconsistency
BMM agents were looking for VCS config at wrong path:
- Old: bmad-core/vcs-config.yaml (incorrect)
- New: .bmad/vcs-config.yaml (correct per BMVCS spec)
IMPACT:
VCS integration failed without manual workaround
FIX:
Updated 3 agent files to use correct path:
- src/modules/bmm/agents/architect.md (line 17)
- src/modules/bmm/agents/pm.md (line 17)
- src/modules/bmm/agents/dev.md (line 22)
TESTING:
Discovered during BMVCS Alpha Phase 2 testing
- Workaround documented, now properly fixed in source
- Test results: ~/test-bmvcs-install/testing/
AFFECTED AGENTS:
✅ Architect - VCS-aware documentation generation
✅ PM - VCS-aware requirements planning
✅ Dev - VCS-aware implementation guidance
This fix enables seamless VCS integration without manual intervention.
Related: #661
Testing: Alpha Phase 2 complete (2025-10-01)
|
2025-10-01 22:28:52 +03:00 |
|
Serhii
|
3f79f1f80a
|
feat(bmvcs): add VCS integration and BMM agent updates
Add VCS setup workflow and integrate with BMM agents:
BMVCS Workflows:
- workflows/setup-vcs/instructions.md: Comprehensive VCS discovery guide
with auto-detection, clarifying questions, and edge case handling
- workflows/setup-vcs/checklist.md: Pre/during/post setup validation
- workflows/setup-vcs/workflow.yaml: Machine-readable workflow definition
BMM Agent Integration:
- architect.md: Added VCS-aware architecture documentation adaptation
- pm.md: Added VCS-aware requirements and release planning
- dev.md: Added VCS-aware code delivery and commit practices
Agents now check bmad-core/vcs-config.yaml and adapt their output to
the configured workflow (GitHub Flow, GitFlow, Trunk-Based, No VCS, etc.)
without imposing new processes on teams.
Part 5/5 of BMVCS migration (#661)
Completes VCS-agnostic module integration
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
2025-09-30 20:12:03 +03:00 |
Brian Madison