BMAD-METHOD

Commit Graph

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	3a0d712f41	chore: bump version to 6.1.0-Beta.2 GSD-style guardrails Phase 1 and Phase 2 complete: - Completion artifacts and verification gates - Pattern extraction and step enumeration - Auto-fix prerequisites and orchestrator reconciliation All tests passing, documentation built successfully.	2026-01-27 02:50:52 -05:00
Jonah Schulte	23f2153f01	feat(workflows): implement GSD-style guardrails Phase 1 Implement enforcement-based workflow patterns to fix chronic reliability issues (story file updates failing 40% of the time, agents skipping work). ## Key Improvements ### 1. Auto-Fix Missing Prerequisites (Guardrail 1) - Workflows now auto-create missing story files and gap analysis - No more blocking errors - self-healing approach - Follows "mind the gap, mend the gap" philosophy Files: super-dev-pipeline/workflow.md, batch-super-dev/workflow.md ### 2. File-Based Completion Verification (Guardrail 2) - All 4 agents (builder, inspector, reviewer, fixer) create completion.json artifacts - Binary verification: file exists = work done (simple, reliable) - Orchestrator parses JSON for structured data (no complex output parsing) Files: agents/builder.md, agents/inspector.md, agents/reviewer.md, agents/fixer.md ### 3. Verification Gates (Guardrail 4) - Hard stops after each agent phase - Verify completion artifact exists - Verify claimed files actually exist - Clear error messages if verification fails File: super-dev-pipeline/workflow.md ### 4. Orchestrator-Driven Reconciliation - Orchestrator (not agents) updates story files - Uses completion artifacts for reliable data - Mechanical task with verification built-in - Auto-fix if updates fail Files: super-dev-pipeline/workflow.md, batch-super-dev/workflow.md ## Documentation - Created: docs/sprint-artifacts/completions/README.md * Documents completion artifact contract * Example artifacts for each agent type * Verification flow diagrams - Created: docs/implementation-notes/gsd-style-guardrails-phase1.md * Complete implementation summary * Testing checklist * Success metrics and rollback strategy ## Benefits ✅ Story file updates: 60% → targeting 100% success ✅ Binary verification: file exists or doesn't (no ambiguity) ✅ Self-healing: auto-fixes missing prerequisites ✅ Hard stops: prevents proceeding with bad state ✅ Auditable: JSON artifacts version controlled ✅ Debuggable: can inspect artifacts when issues occur ## Files Changed Modified (6): - super-dev-pipeline/workflow.md (~100 lines) - batch-super-dev/workflow.md (~80 lines) - agents/builder.md (~30 lines) - agents/inspector.md (~25 lines) - agents/reviewer.md (~30 lines) - agents/fixer.md (~35 lines) Created (2): - docs/sprint-artifacts/completions/README.md - docs/implementation-notes/gsd-style-guardrails-phase1.md Total: ~300 lines of enforcement-based improvements ## Next Steps (Phase 2) - Remove redundant Reconciler agent (-227 lines) - Extract common patterns to patterns/ directory - Add explicit step enumeration (14-step checklist) Part of: v6.1.0-Beta.1 Related: GSD-style refactoring plan	2026-01-27 02:32:45 -05:00

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

3a0d712f41

chore: bump version to 6.1.0-Beta.2

GSD-style guardrails Phase 1 and Phase 2 complete:
- Completion artifacts and verification gates
- Pattern extraction and step enumeration
- Auto-fix prerequisites and orchestrator reconciliation

All tests passing, documentation built successfully.

2026-01-27 02:50:52 -05:00

Jonah Schulte

23f2153f01

feat(workflows): implement GSD-style guardrails Phase 1

Implement enforcement-based workflow patterns to fix chronic reliability issues
(story file updates failing 40% of the time, agents skipping work).

## Key Improvements

### 1. Auto-Fix Missing Prerequisites (Guardrail 1)
- Workflows now auto-create missing story files and gap analysis
- No more blocking errors - self-healing approach
- Follows "mind the gap, mend the gap" philosophy

Files: super-dev-pipeline/workflow.md, batch-super-dev/workflow.md

### 2. File-Based Completion Verification (Guardrail 2)
- All 4 agents (builder, inspector, reviewer, fixer) create completion.json artifacts
- Binary verification: file exists = work done (simple, reliable)
- Orchestrator parses JSON for structured data (no complex output parsing)

Files: agents/builder.md, agents/inspector.md, agents/reviewer.md, agents/fixer.md

### 3. Verification Gates (Guardrail 4)
- Hard stops after each agent phase
- Verify completion artifact exists
- Verify claimed files actually exist
- Clear error messages if verification fails

File: super-dev-pipeline/workflow.md

### 4. Orchestrator-Driven Reconciliation
- Orchestrator (not agents) updates story files
- Uses completion artifacts for reliable data
- Mechanical task with verification built-in
- Auto-fix if updates fail

Files: super-dev-pipeline/workflow.md, batch-super-dev/workflow.md

## Documentation

- Created: docs/sprint-artifacts/completions/README.md
  * Documents completion artifact contract
  * Example artifacts for each agent type
  * Verification flow diagrams

- Created: docs/implementation-notes/gsd-style-guardrails-phase1.md
  * Complete implementation summary
  * Testing checklist
  * Success metrics and rollback strategy

## Benefits

✅ Story file updates: 60% → targeting 100% success
✅ Binary verification: file exists or doesn't (no ambiguity)
✅ Self-healing: auto-fixes missing prerequisites
✅ Hard stops: prevents proceeding with bad state
✅ Auditable: JSON artifacts version controlled
✅ Debuggable: can inspect artifacts when issues occur

## Files Changed

Modified (6):
- super-dev-pipeline/workflow.md (~100 lines)
- batch-super-dev/workflow.md (~80 lines)
- agents/builder.md (~30 lines)
- agents/inspector.md (~25 lines)
- agents/reviewer.md (~30 lines)
- agents/fixer.md (~35 lines)

Created (2):
- docs/sprint-artifacts/completions/README.md
- docs/implementation-notes/gsd-style-guardrails-phase1.md

Total: ~300 lines of enforcement-based improvements

## Next Steps (Phase 2)

- Remove redundant Reconciler agent (-227 lines)
- Extract common patterns to patterns/ directory
- Add explicit step enumeration (14-step checklist)

Part of: v6.1.0-Beta.1
Related: GSD-style refactoring plan

2026-01-27 02:32:45 -05:00

3 Commits