Jonah Schulte
|
90010f8ef9
|
feat(batch-super-dev): add git commit queue + stricter story validation
Addresses two critical production issues discovered during real usage:
ISSUE #1: Git Lock File Conflicts in Parallel Mode
----------------------------------------------------
Multiple parallel agents trying to commit simultaneously caused:
- .git/index.lock conflicts
- "Another git process is running" errors
- Required manual intervention to resolve
SOLUTION: Git Commit Queue with File-Based Locking
- Workers acquire .git/bmad-commit.lock before committing
- Automatic retry with exponential backoff (1s → 30s)
- Stale lock cleanup (>5 min old locks auto-removed)
- Timeout protection (max 5 min wait, then HALT)
- Serializes commits while keeping implementations parallel
- Zero user intervention needed
Implementation:
- super-dev-pipeline/step-06-complete.md: Added commit queue logic
- super-dev-pipeline/step-06a-queue-commit.md: NEW documentation file
- .gitignore: Added .git/bmad-commit.lock
ISSUE #2: 0-Task Stories Classified as COMPLEX
-----------------------------------------------
Real example from production:
- "11-4-classes-workshops-advanced": 0 tasks, high-risk keywords
- Classified as COMPLEX (risk keywords triggered it)
- Proceeded to implementation → agent had nothing to do → failed
SOLUTION: Minimum 3-Task Requirement
- Step 2.5 validation now rejects stories with <3 tasks
- Step 2.6 complexity scoring marks <3 tasks as INVALID
- INVALID stories filtered out before user selection
- Clear error message directs user to /validate-create-story
Validation Rules:
- 0-2 tasks: INVALID (stub/incomplete)
- 3 tasks: Minimum valid (MICRO threshold)
- 4-15 tasks: STANDARD
- 16+ tasks: COMPLEX
Implementation:
- batch-super-dev/instructions.md:
- Step 2.5: Added <3 task check with detailed error message
- Step 2.6: Added INVALID classification for <3 tasks
- End of Step 2.6: Filter INVALID stories before selection
- batch-super-dev/README.md: Documented validation rules
- CHANGELOG.md: Comprehensive documentation of both features
Impact:
- Commit queue: Eliminates 100% of git lock file conflicts
- Story validation: Prevents wasted tokens on incomplete stories
- Combined: Production-ready parallel batch processing
|
2026-01-07 20:10:49 -05:00 |