- Remove autonomous-epic workflow from BMM and BMGD modules
- Remove agent menu entries for autonomous-epic
- Update workflow references to use batch-super-dev
- Add README-changes.md documenting fork customizations
- Remove outdated SPRINT-STATUS-SYNC-GUIDE.md
batch-super-dev is the superior approach with proactive story
validation, auto-creation of missing stories, and smart reconciliation.
- Add auto-detection of project root and story directories
- Enable scripts to work from any working directory
- Add explicit path override options via CLI arguments
- Improve error messages with suggested paths when files not found
- Update smart batching to show options only when time_saved > 0
- Reduce decision fatigue by skipping batching menu when no benefit
Resolved conflict in autonomous-epic/workflow.yaml by:
- Accepting origin/main's cleaner naming: .autonomous-epic-{epic_num}-progress.yaml
- Adding backwards compatibility to check both new and legacy formats
- Updated all progress file references to use dynamic {{progress_file_path}}
Changes:
- workflow.yaml: Use new naming convention
- instructions.xml: Check for both formats (new + legacy) on resume
- README.md: Document backwards compatibility
This ensures no in-progress epics are missed when upgrading between versions.
- Change tracking file from `.autonomous-epic-progress.yaml` to
`.autonomous-epic-progress-epic-{{epic_num}}.yaml`
- Prevents race conditions when multiple epics run in parallel
- Each epic now maintains isolated tracking state
- Updates: README.md, instructions.xml (4 locations), workflow.yaml
Resolves issue where parallel epic processing would stomp on
shared tracking file causing data loss and synchronization issues
* docs: chose your tea engagement
* docs: addressed PR comments
* docs: made refiements to the mermaid diagram
* docs: wired in test architect discoverability nudges
---------
Co-authored-by: Brian <bmadcode@gmail.com>
This commit integrates the story-pipeline workflow (PR #1194) with autonomous-epic
and adds post-implementation validation to catch false positives.
MAJOR CHANGES:
1. Merged story-pipeline workflow from upstream PR #1194 (20 files, 4,564 additions)
2. Added post-validation step (step-05b) between implementation and code review
3. Integrated story-pipeline as the default workflow for autonomous-epic
4. Replaced super-dev-story with story-pipeline in batch mode
NEW FEATURES:
- Post-implementation validation (step-05b-post-validation.md)
* Verifies completed tasks against actual codebase
* Catches false positives (tasks marked done but not implemented)
* Re-runs implementation if gaps found
* Uses Glob/Grep/Read to verify file existence and completeness
BENEFITS:
- Token efficiency: 25-30K per story (vs 100-150K with super-dev-story)
- 65% token savings per story, 75% savings per epic
- All super-dev-story quality gates PLUS post-validation
- Checkpoint/resume capability for long stories
- Batch mode for fully unattended execution
ARCHITECTURE:
- autonomous-epic orchestrates epic-level processing
- story-pipeline handles single-story lifecycle (9 steps including 5b)
- Role-switching in same session (vs separate workflow calls)
- Single session per story = massive token savings
TIME ESTIMATES (updated):
- Small epic (3-5 stories): 2-4 hours (was 3-6 hours)
- Medium epic (6-10 stories): 4-8 hours (was 6-12 hours)
- Large epic (11+ stories): 8-16 hours (was 12-24 hours)
FILES MODIFIED:
- autonomous-epic/instructions.xml (integrated story-pipeline)
- autonomous-epic/workflow.yaml (updated settings, removed super-dev choice)
- story-pipeline/* (20 new files from PR #1194)
- story-pipeline/steps/step-05-implement.md (points to step-05b)
- story-pipeline/workflow.md (added step 5b to map and gates)
- story-pipeline/workflow.yaml (added step 5b definition)
- story-pipeline/templates/*.yaml → *.yaml.template (renamed to avoid linting)
FILES ADDED:
- story-pipeline/steps/step-05b-post-validation.md (NEW)
- INTEGRATION-NOTES.md (comprehensive documentation)
TESTING:
- PR #1194 validated with real User Invitation system story
- 17 files, 2,800+ lines generated successfully
- Context exhaustion recovery tested
See INTEGRATION-NOTES.md for full details.
Co-authored-by: tjetzinger (story-pipeline PR #1194)
- Add create-story-with-gap-analysis workflow for verified codebase scanning at planning time
- Fix autonomous-epic to support parallel execution (no auto-branch creation)
- Fix autonomous-epic and super-dev-story to auto-accept gap analysis in autonomous mode
- Fix push-all to support targeted file commits (safe for parallel agents)
- Update dev-story and super-dev-story to pass auto_accept_gap_analysis parameter
- Add explicit autonomous mode instructions to workflows
Breaking changes: None - all enhancements are backward compatible
- Each story now commits and pushes after completion
- Auto-generated commit messages per story
- Safety checks run before each push
- Continues on push failures (doesn't halt entire epic)
- All changes backed up to remote incrementally
Ensures epic progress is saved to remote as work completes
- New /push-all workflow for commit and push with safety
- Can be used anywhere (not just in super-dev-story)
- Comprehensive safety checks (secrets, API keys, large files)
- Smart commit message generation (conventional commits)
- Handles push failures (rebase, upstream, auth)
- Registered in Dev and SM agent menus
- Also integrated into super-dev-story Step 11
Applies to both BMM and BMGD modules
- New /autonomous-epic command processes entire epic
- Just-in-time planning: creates each story before developing
- Auto-develops using super-dev-story or dev-story
- Progress tracking with resume capability
- Git commits after each story completion
- Error handling with retry logic and continue-on-failure
- Epic completion report with statistics
- Estimated: 100K-150K tokens per story
Use cases:
- Overnight epic completion
- CI/CD integration
- Batch sprint processing
Applies to both BMM and BMGD modules
- New /super-dev-story command for comprehensive validation
- Includes all dev-story steps PLUS:
- Step 9.5: Post-dev gap analysis (verify completion)
- Step 9.6: Automated code review (catch issues)
- Auto-fixes issues and loops back if gaps/problems found
- Max iteration safety (default 3 cycles)
- Opt-in via separate command (not forced)
- ~30% more tokens but prevents review rework cycles
Applies to both BMM and BMGD modules
- Audit completed stories to verify claims match code
- Validate any story without starting development
- Detect false positives (marked done but not implemented)
- Batch mode to audit multiple stories
- Generate audit reports for team review
Applies to both BMM and BMGD modules
- Add Step 1.5 gap analysis before development starts
- Scan codebase to validate draft tasks against reality
- Propose task refinements (add/modify/remove)
- Six user options: approve, auto-accept, reject, edit, skip, review
- Update story file with Gap Analysis section
- Prevents duplicate implementations in batch planning
Applies to both BMM and BMGD modules
- Remove codebase scanning from planning phase
- Mark generated tasks as DRAFT
- Add notation that tasks will be validated at dev-time
- Focus on requirements analysis and architecture context
- Simplify workflow by deferring gap analysis to execution
Applies to both BMM and BMGD modules
Major improvements:
- All agents now use consistent 2-letter menu codes (compound triggers)
- Phase 1-3 workflows updated to use planning_artifacts folder
- Windows installer fixed with inquirer multiselection resolution
- Chat and party mode auto-injected into all agents
- All agents pass comprehensive validation checks
- Restored agent files from Docusaurus merge
* docs: remove dead links in test architecture documentation
* docs: updated test architecture documentation for clarity and consistenc
* docs: update test architecture documentation for clarity and consistency
* docs: addressed PR comments
- 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>