NEXT_SESSION.md is useful for testing but should not be in the
development branch. Can be recreated in a separate testing branch
if needed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* Port TEA commands into workflows and preload Murat knowledge
* Broke the giant knowledge dump into curated fragments under src/modules/bmm/testarch/knowledge/
* Broke the giant knowledge dump into curated fragments under src/modules/bmm/testarch/knowledge/
* updated the web bunles for tea, and spot updates for analyst and sm
* Replaced the old TEA brief with an indexed knowledge system: the agent now loads topic-specific
docs from knowledge/ via tea-index.csv, workflows reference those fragments, and risk/level/
priority guidance lives in the new fragment files
---------
Co-authored-by: Murat Ozcan <murat@mac.lan>
- Add blank line before list in Error Handling section
- Improve markdown compliance
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Add comprehensive DEVELOPMENT_APPROACH.md document
- Document direct development vs BMB create-module comparison
- Include compliance matrix with BMAD v6 standards
- Add recommendations for future module development
- Fix markdown formatting and URL links in README
- Add new doc to Documentation section
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add practical examples demonstrating VCS-agnostic adaptation:
- vcs-adaptation-examples.md: 6 real-world scenarios (GitHub Flow,
GitFlow, No VCS, SVN, Trunk-Based, Multi-VCS)
- vcs-detection-implementation.py: Reference implementation of Git
workflow auto-detection with confidence scoring
- examples/README.md: Guide to using examples and integration
Examples demonstrate "Detection as a HINT, not a DECISION" principle
with evidence-based suggestions and user confirmation.
Part 4/5 of BMVCS migration (#661)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add comprehensive documentation for VCS-agnostic approach:
- VCS_AGNOSTIC_PRINCIPLES.md: Core philosophy and 10 principles
- VCS_AGNOSTIC_PROPOSAL.md: Implementation approach and examples
- VCS_DETECTION_CONFIDENCE.md: Auto-detection confidence scoring
- docs/README.md: Documentation overview and quick start
Documentation explains how BMAD adapts to any VCS (Git, SVN, Perforce,
or no VCS) with appropriate terminology and workflow patterns.
Part 3/5 of BMVCS migration (#661)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Add 5 VCS adaptation templates for different workflows:
- git-github-flow.yaml: Simple feature branches (40% of users)
- git-gitflow.yaml: Structured releases (20% of users)
- git-trunk-based.yaml: Continuous deployment (15% of users)
- no-vcs.yaml: Prototypes and one-time scripts (5% of users)
- custom-generic.yaml: Custom/legacy VCS systems (10% of users)
Templates support VCS-agnostic artifact generation across all BMAD agents.
Part 2/5 of BMVCS migration (#661)
Completes core VCS discovery functionality
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Port discover-vcs.md from PR #582 (187 lines)
- Port create-vcs-adapted-doc.md from PR #583 (165 lines)
- Add validate-vcs-config.md task (73 lines new)
- Add installer.js for module setup (26 lines)
Part 2/5 of BMVCS migration (#661) - Tasks Complete
Note: VCS templates to be added in next commit after proper extraction
Next: Manually create 5 VCS templates with valid YAML
- Created agent-activation-web.xml with bundled file access instructions
- Updated web-bundler to inject web activation into all agent bundles
- Agents now understand how to access <file> elements instead of filesystem
- Includes workflow execution instructions for bundled environments
- Generated new web bundles with activation blocks
Serhii
Brian Madison
Murat K Ozcan
Murat Ozcan