Jonah Schulte
|
b517a8b1d0
|
Add batch-super-dev workflow with auto-installation and quality gates
Features:
- Interactive batch selector for processing multiple ready-for-dev stories
- 5-layer quality gate system (pre-gap, post-validation, reconciliation, code review, sprint-status sync)
- Smart story reconciliation (auto-updates checkboxes based on Dev Agent Record)
- Anti-vibe-coding enforcement (verifies files exist, tests pass, implementations aren't stubs)
- Story validation & auto-creation (validates 12 BMAD sections, creates missing stories)
- Auto-generates /batch-super-dev and /super-dev-pipeline slash commands on installation
Platform Support:
- Claude Code: Auto-creates .claude-commands/batch-super-dev.md
- Windsurf: Auto-creates slash commands for cross-compatibility
Workflow Location:
- Source: src/modules/bmm/workflows/4-implementation/batch-super-dev/
- Installed: _bmad/bmm/workflows/4-implementation/batch-super-dev/
Quality Gates:
1. Pre-gap analysis validates story completeness
2. Post-implementation validation verifies every task (anti-vibe-coding)
3. Smart reconciliation updates checkboxes based on evidence
4. Multi-agent code review finds issues before commit
5. Python script validates sprint-status.yaml accuracy
|
2026-01-07 12:12:13 -05:00 |
|
Jonah Schulte
|
73b8190e7b
|
feat(validation): Add comprehensive story validation system with Haiku agents
VALIDATION WORKFLOWS (6 total):
- validate-story: Quick task checkbox validation
- validate-story-deep: Deep code verification with Haiku agent
- validate-all-stories: Batch quick validation
- validate-all-stories-deep: Comprehensive platform audit
- validate-epic-status: Per-epic validation
- validate-all-epics: All epics validation
VALIDATION SCRIPTS (4 total):
- sprint-status-updater.py: Compare story files vs sprint-status.yaml
- task-verification-engine.py: Python-based task verification
- llm-task-verifier.py: LLM-powered verification (alternative)
- add-status-fields.py: Add Status field to stories
HAIKU AGENT APPROACH:
- One agent per story (not per task - avoids 99% overhead)
- Agent reads actual code with Glob/Read tools
- Verifies stubs vs real implementation
- Checks multi-tenant, error handling, tests
- Evidence-based verification (line numbers, code snippets)
COST OPTIMIZATION:
- Haiku: $0.15/story vs Sonnet: $1.80/story (92% savings)
- Full platform: $76 vs $920 (saves $844)
- Batching: 5 concurrent agents (prevents overload)
CAPABILITIES:
- False positive detection (checked but code missing)
- False negative detection (unchecked but code exists)
- Code quality review (TODOs, stubs, missing features)
- Status recommendation (done/review/in-progress)
- Automated status updates
DOCUMENTATION:
- HOW-TO-VALIDATE-SPRINT-STATUS.md
- SPRINT-STATUS-VALIDATION-COMPLETE.md
- Slash command docs in .claude-commands/
USE CASES:
- Weekly: Quick validation (free, 5 sec)
- Pre-done: Deep story check ($0.15, 2-5 min)
- Pre-launch: Full audit ($76, 4-6h)
- Quality sweep: Phase 3 comprehensive validation
Enables bulletproof production confidence for any BMAD project.
|
2026-01-02 19:20:11 -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 |
|
Jonah Schulte
|
a14ab30b40
|
docs: add comprehensive PR description for story-pipeline integration
|
2025-12-27 23:01:05 -05:00 |