* fix(docs): align sidebar with actual docs structure and fix image path
Sidebar referenced non-existent paths (modules/bmm/, getting-started/, etc.)
while actual docs live in different locations (modules/bmm-bmad-method/,
bmad-core-concepts/, etc.). Updated sidebar to match reality so Docusaurus
can build successfully.
Also fixed broken image reference in workflows-guide.md that used an
incorrect relative path.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix(docs): update build script to include docs/modules directory
The build script was excluding the modules folder when copying from docs/,
but module docs now live in docs/modules/ instead of src/modules/*/docs/.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
* fix(docs): correct broken internal links
Fixed relative paths that were pointing to non-existent locations:
- bmgd index: ../../bmm/docs/index.md → ../bmm/index.md
- cis index: ../../bmm/docs/index.md → ../bmm/index.md
- bmm faq: ./README.md → GitHub URL
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
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.
- Add --epic flag to filter validation to specific epic (e.g., epic-1)
- Add --mode flag with 'validate' and 'fix' options
- Filter logic extracts epic number and matches story file prefixes
- Enables per-epic validation for validate-all-epics workflow
Part of: validate-all-epics workflow infrastructure
- 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>
Major features:
- Unified Agent Workflow: Create/Edit/Validate consolidated into single workflow
- Agent Knowledge System: Comprehensive data file architecture for agent building
- Deep Language Integration: All sharded workflows support language choice
- Core Module Documentation: New docs for brainstorming, party mode, advanced elicitation
- BMAD Core Concepts: New documentation structure for agents, workflows, modules
- Create-Tech-Spec Sharded: Converted to sharded format with orient-first pattern
466 files changed, 12,983 insertions(+), 12,047 deletions(-)
- Renamed package to @jschulte/bmad-method (scoped package)
- Updated version to 6.0.0-alpha.22
- Updated repository URL to jschulte/BMAD-METHOD
- Added .npmignore to exclude dev files
- Enhanced description to mention story-pipeline
This allows users to install via:
npx @jschulte/bmad-method install
Integrates the bmad-guide skill into BMAD installation process to help
Claude stay on track with BMAD methodology.
Features:
- Phase navigation and workflow selection guidance
- Project level detection (0-4) for routing to correct workflows
- Common mistakes prevention (skipping phases, manual coding)
- Emergency recovery procedures when off track
- Quick reference tables and troubleshooting
Implementation:
- Created resources/skills/ directory with bmad-guide.md (428 lines)
- Added installBmadGuideSkill() to ClaudeCodeSetup class
- Skill auto-installs to ~/.claude/skills/ during setup
- Available globally across all BMAD projects
- Updated installation documentation
Usage:
- Automatic: Skill is installed when running npx bmad-method install
- Manual access: /bmad-guide command in any project
- Optional: Add BMAD Method config to ~/.claude/CLAUDE.md for automatic invocation
Benefits:
- Prevents Claude from jumping straight to coding without workflows
- Ensures proper phase progression
- Guides workflow selection based on project level
- Self-corrects when going off track
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