ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
1,382 Commits 62 Branches 141 Tags 74 MiB
Commit Graph

5 Commits

Author SHA1 Message Date
Jonah Schulte 2526e7c9cb refactor: rename workflows for clarity 
Renamed three implementation workflows to avoid confusion:
- batch-super-dev → batch-stories (processes multiple stories)
- super-dev-pipeline → story-full-pipeline (single story with validation/review)
- story-pipeline → story-dev-only (basic TDD implementation only)

Changes include:
- Renamed workflow directories
- Updated workflow.yaml name fields and installed_path references
- Updated all cross-references in workflow.md files
- Updated state file naming conventions for clarity
- Updated references in documentation and other workflows

This naming convention eliminates pattern-matching confusion by using
completely distinct names for each workflow level.
 2026-01-28 02:47:19 -05:00
Jonah Schulte d3bf02a0af refactor: consolidate super-dev-pipeline architecture and clarify execution modes 
**Removed:**
- -v2 suffix from super-dev-pipeline (consolidated to single pipeline)
- Old v1.6.0 single-agent pipeline (replaced by v2.0 multi-agent)

**Updated:**
- batch-super-dev execution modes simplified to S (sequential) and P (parallel)
- Both S and P now use Task agents to keep story context out of main thread
- P mode uses smart wave-based execution with dependency analysis
- Sequential mode (S): One Task agent at a time, no dependency analysis
- Parallel mode (P): Wave-based execution respecting story dependencies

**Architecture:**
- Story-level: S (sequential Task agents) vs P (parallel Task agents with waves)
- Within-story: Always multi-agent (builder/inspector/reviewer/fixer)
- Main thread stays clean - all story implementation in Task agent context

**Version:** 6.0.0-Beta.3 → 6.0.0-Beta.4
 2026-01-26 19:40:23 -05:00
Jonah Schulte 7c1051b017 refactor: remove autonomous-epic in favor of batch-super-dev 
- 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.
 2026-01-07 16:00:32 -05:00
Jonah Schulte 0ff7099af7 feat: add smart batching to super-dev-pipeline for repetitive work 
Add intelligent task grouping that automatically detects and batches
similar low-risk tasks while maintaining full validation discipline.

KEY INNOVATION:
Smart batching is NOT vibe coding - it's systematic pattern detection
with batch validation and automatic fallback to individual execution.

PROBLEM SOLVED:
- One-task-at-a-time is too slow for repetitive work
- 100 package installations × 2min = 200 minutes (unnecessarily slow)
- Pattern: Add package → install → build is repeated 100 times identically

SMART BATCHING SOLUTION:
- Step 2: Detect batchable patterns in pre-gap analysis
- Step 3: Execute similar tasks together, validate as batch
- Fallback: If batch fails, revert to one-at-a-time for that batch
- Safety: High-risk tasks NEVER batched

BATCHABLE PATTERNS (low risk):
- Package installations (validated by build)
- Module registrations (validated by TypeScript)
- Code deletions (validated by tests)
- Import updates (validated by build)

NON-BATCHABLE (individual execution):
- Business logic (varies per case)
- Security code (high risk)
- Data migrations (irreversible)
- Novel patterns (unproven)

TIME SAVINGS:
- Example: 100-task story with 80 batchable + 20 individual
- Without batching: 100 × 2min = 200 minutes
- With batching: 5 batches × 10min + 20 × 2min = 90 minutes
- Savings: 110 minutes (55% faster!)

FEATURES ADDED:
- Pattern detection in step-02-pre-gap-analysis.md
- Batch execution in step-03-implement.md
- Batching configuration in workflow.yaml
- Smart batching documentation in workflow.md and README.md

SAFETY MECHANISMS:
- Conservative pattern detection (default to individual)
- Explicit validation strategy per batch
- Automatic fallback if batch fails
- High-risk tasks never batched
- All quality gates still enforced

VERSION:
- super-dev-pipeline: 1.0.0 → 1.1.0 (smart batching added)

INSTALLATIONS:
- craftedcall: Updated with smart batching
- usmax-nda: Updated with smart batching

This solves the velocity problem while maintaining anti-vibe-coding discipline!
 2025-12-28 23:49:53 -05:00
Jonah Schulte d4b8246bd9 feat: add super-dev-pipeline for brownfield + anti-vibe-coding enforcement 
Create new super-dev-pipeline workflow that solves critical issues:
1. Works for BOTH greenfield AND brownfield development
2. Uses step-file architecture to prevent vibe coding at high token counts
3. Adaptive implementation (TDD for new, refactor for existing)
4. All quality gates with disciplined execution

PROBLEM SOLVED:
- story-pipeline assumes greenfield (ATDD doesn't work for brownfield)
- super-dev-story allows vibe coding when tokens >100K
- Need workflow that handles real-world scenarios (most work is brownfield!)

NEW WORKFLOW: super-dev-pipeline
- 7 step files with mandatory sequences
- Detects greenfield vs brownfield automatically
- Pre-gap analysis validates against existing code
- Adaptive implementation methodology
- Post-validation catches false positives
- Code review finds 3-10 issues
- Anti-vibe-coding enforcement

STEPS:
1. Init - Load story, detect development mode
2. Pre-gap - Validate tasks against codebase (critical for brownfield!)
3. Implement - Adaptive (TDD for new, refactor for existing)
4. Post-validate - Verify completion vs reality
5. Code review - Adversarial (3-10 issues)
6. Complete - Commit + push
7. Summary - Audit trail

BENEFITS:
- Works for greenfield AND brownfield
- 40-60K tokens per story (vs 100-150K for orchestration)
- Prevents vibe coding even at 200K+ tokens
- All super-dev quality gates preserved
- Step-file discipline from story-pipeline

AUTONOMOUS-EPIC UPDATED:
- Now uses super-dev-pipeline instead of story-pipeline
- Handles create-story separately for backlog stories
- More realistic token estimates (40-60K vs 25-30K)
- Updated time estimates

FILES ADDED:
- src/modules/bmm/workflows/4-implementation/super-dev-pipeline/* (14 files)
- .claude-commands/super-dev-pipeline.md
- ~/.codex/prompts/bmad-super-dev-pipeline.md

FILES MODIFIED:
- autonomous-epic/instructions.xml (use super-dev-pipeline)
- autonomous-epic/workflow.yaml (updated settings)

INSTALLATIONS:
- craftedcall: super-dev-pipeline + updated autonomous-epic
- usmax-nda: super-dev-pipeline + updated autonomous-epic

This is the production-ready solution for autonomous epic processing!
 2025-12-28 12:09:06 -05:00