@atlashub/smartstack-cli 4.46.0 → 4.47.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@atlashub/smartstack-cli",
-  "version": "4.46.0",
+  "version": "4.47.0",
   "description": "SmartStack Claude Code automation toolkit - GitFlow, EF Core migrations, prompts and more",
   "author": {
     "name": "SmartStack",

package/templates/skills/business-analyse-develop/SKILL.md

@@ -149,6 +149,8 @@ When the user invokes `/business-analyse-develop`, they are giving you the instr
 - Ask the user to choose between supervised/autonomous mode
 - Wait for user input between modules
 - Delegate the loop to sub-agents (except team mode and /apex delegation)
+- Display a progress report then ask "shall I continue?" or present options (1/2/3)
+- Pause because the scope is "large" or "ambitious" — execute ALL of it regardless of size
 
 **The ONLY valid stop conditions are:**
 - ALL objectives met / ALL tasks completed (→ report)

package/templates/skills/business-analyse-develop/steps/step-00-init.md

@@ -58,6 +58,8 @@ Ralph-loop is FULLY AUTONOMOUS by default. It executes ALL tasks from start to f
 
 **DO NOT** ask the user to confirm, choose a mode, or approve execution.
 **DO NOT** set max_iterations = 1 or any reduced value.
+**DO NOT** display a progress report and then ask "shall I continue?" or present numbered options.
+**DO NOT** pause because the scope seems large — 500+ files across 11 modules is NORMAL. Execute ALL of it.
 
 The loop runs autonomously until:
 - ALL tasks are completed (success)

package/templates/skills/business-analyse-develop/steps/step-01-v4-execute.md

@@ -7,6 +7,12 @@ next_step: steps/step-02-v4-verify.md
 
 # Step 01-v4: Continuous Module Execution
 
+## EXECUTION GUARANTEE — AUTONOMY RULES (MANDATORY)
+
+> **NEVER stop between modules.** NEVER ask "shall I continue?". NEVER present options (1/2/3).
+> **NEVER pause after a progress report.** Progress reports are LOG OUTPUT ONLY — print them and IMMEDIATELY continue to the next module.
+> **The user invoked /business-analyse-develop to execute ALL modules to completion.** That is your mandate. Any stop that is not: all-complete, dead-end, or Ctrl+C is a **VIOLATION**.
+
 ## YOUR TASK
 
 For each module in topological order, delegate the ENTIRE module implementation to `/apex -d` in a continuous session. Run quality gates at natural checkpoints. Let server-side compaction manage context.
@@ -102,12 +108,14 @@ grep -rn "Assert.True(true)\|Assert.Pass()\|// TODO\|throw new NotImplementedExc
 
 If found → delegate fix to apex: "Replace stub tests with real implementations"
 
-### 7. Module Complete
+### 7. Module Complete — CONTINUE IMMEDIATELY
 
 When ALL gates pass for a module:
 1. Log checkpoint: `"Module {moduleCode}: ALL GATES PASS"`
 2. Optionally append to progress.txt (human checkpoint)
-3. Advance to next module in queue
+3. **IMMEDIATELY** advance to next module in queue — DO NOT pause, DO NOT ask user, DO NOT present options
+
+> **ANTI-STOP GUARD:** After logging the progress report, your VERY NEXT action MUST be starting the next module delegation (`/apex -d`). If there are no more modules, go to step-02-v4-verify. Outputting a progress report and then waiting for user input is a **VIOLATION** of the execution guarantee.
 
 ---