From 3f5b975d885ca93719ae6cdc7a7e2fc597c68c38 Mon Sep 17 00:00:00 2001 From: Jonah Schulte Date: Sun, 25 Jan 2026 23:54:26 -0500 Subject: [PATCH] chore: bump version to 6.3.4-alpha.23 All tests passing (352/352). Simplified execution mode prompt (removed confusing language). Ready for npm publish. --- package-lock.json | 4 ++-- package.json | 2 +- .../batch-super-dev/instructions.md | 18 +++++------------- 3 files changed, 8 insertions(+), 16 deletions(-) diff --git a/package-lock.json b/package-lock.json index e3abb61c..3dd92c06 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@jonahschulte/bmad-method", - "version": "6.3.3-alpha.23", + "version": "6.3.4-alpha.23", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@jonahschulte/bmad-method", - "version": "6.3.3-alpha.23", + "version": "6.3.4-alpha.23", "license": "MIT", "dependencies": { "@clack/prompts": "^0.11.0", diff --git a/package.json b/package.json index 1a1ab054..0ece2b22 100644 --- a/package.json +++ b/package.json @@ -1,7 +1,7 @@ { "$schema": "https://json.schemastore.org/package.json", "name": "@jonahschulte/bmad-method", - "version": "6.3.3-alpha.23", + "version": "6.3.4-alpha.23", "description": "Breakthrough Method of Agile AI-driven Development (Enhanced with hospital-grade quality, TDD, and intelligent multi-agent review)", "keywords": [ "agile", diff --git a/src/modules/bmm/workflows/4-implementation/batch-super-dev/instructions.md b/src/modules/bmm/workflows/4-implementation/batch-super-dev/instructions.md index dd1757f6..230ccdab 100644 --- a/src/modules/bmm/workflows/4-implementation/batch-super-dev/instructions.md +++ b/src/modules/bmm/workflows/4-implementation/batch-super-dev/instructions.md @@ -736,24 +736,16 @@ Lives are at stake. All code must meet safety-critical reliability standards. **Choose execution mode:** -[I] INTERACTIVE CHECKPOINT MODE (Recommended for oversight) +[I] INTERACTIVE CHECKPOINT MODE - After each story completes, pause for your review - You approve before proceeding to next story - Allows course correction if issues detected - - Best for: Critical features, new team members, complex epics + - Best for: When you want to monitor progress -[A] FULLY AUTONOMOUS MODE (Maximum quality, zero interaction) +[A] FULLY AUTONOMOUS MODE - Process all selected stories without pausing - - ENHANCED quality standards (even more rigorous than interactive) - - Hospital-grade code verification at every step - - NO shortcuts, NO skimping, NO corner-cutting - - Best for: Well-defined stories, experienced implementation - -⚠️ AUTONOMOUS MODE = HIGHER QUALITY, NOT LOWER -In autonomous mode, quality standards are ENHANCED because there's no -human oversight in the loop. Every decision is double-checked. - -QUALITY >> DURATION. We prioritize correctness over speed. + - No human interaction until completion + - Best for: When stories are well-defined and you trust the process Which mode? [I/A]: