specflow-cc 1.11.0 → 1.11.1

package/CHANGELOG.md

@@ -5,6 +5,19 @@ All notable changes to SpecFlow will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.11.1] - 2026-02-10
+
+### Fixed
+
+- **Orchestrator premature state advancement** — executor agents could advance STATE.md beyond "review", skipping the review step entirely
+  - After `/sf:run` completion, the orchestrator would sometimes perform `/sf:done` logic (moving spec to Completed, activating next spec)
+  - Root cause: vague instructions in STATE.md update step allowed LLM agents to over-interpret "update STATE.md"
+  - Added explicit boundary instructions ("DO NOT move to Completed, DO NOT activate next spec") to all three executor agents
+  - Added post-execution state verification guard in `/sf:run` command handler
+  - Affected files: `sf-spec-executor-orchestrator.md`, `spec-executor-orchestrator.md`, `spec-executor.md`, `run.md`
+
+---
+
 ## [1.11.0] - 2026-02-06
 
 ### Added

package/README.md

@@ -17,7 +17,7 @@ npx specflow-cc --global
 
 <br>
 
-https://github.com/user-attachments/assets/3f516907-8657-4ea4-bc0c-6319998a09db
+https://github.com/user-attachments/assets/23415009-81f9-4755-9e35-32e8bc56b8e7
 
 <br>
 

package/agents/sf-spec-executor-orchestrator.md

@@ -385,9 +385,17 @@ Append Execution Summary to specification:
 
 ## Step 8: Update STATE.md
 
+Update ONLY the Current Position section:
 - Status → "review"
 - Next Step → "/sf:review"
 
+**CRITICAL — DO NOT go beyond this:**
+- Do NOT move the spec to Completed Specifications table
+- Do NOT remove the spec from Queue table
+- Do NOT activate the next specification in the queue
+- Do NOT archive the spec file
+- These actions belong to `/sf:done`, not to execution
+
 </process>
 
 <output>

package/agents/spec-executor-orchestrator.md

@@ -687,10 +687,18 @@ rm .specflow/execution/SPEC-XXX-state.json
 
 ## Step 7: Update STATE.md
 
-- Status -> "review"
-- Next Step -> "/sf:review"
+Update ONLY the Current Position section:
+- Status → "review"
+- Next Step → "/sf:review"
 - Remove or update Execution Status row
 
+**CRITICAL — DO NOT go beyond this:**
+- Do NOT move the spec to Completed Specifications table
+- Do NOT remove the spec from Queue table
+- Do NOT activate the next specification in the queue
+- Do NOT archive the spec file
+- These actions belong to `/sf:done`, not to execution
+
 </process>
 
 <output>

package/agents/spec-executor.md

@@ -233,9 +233,17 @@ Append to specification:
 
 ## Step 9: Update STATE.md
 
+Update ONLY the Current Position section:
 - Status → "review"
 - Next Step → "/sf:review"
 
+**CRITICAL — DO NOT go beyond this:**
+- Do NOT move the spec to Completed Specifications table
+- Do NOT remove the spec from Queue table
+- Do NOT activate the next specification in the queue
+- Do NOT archive the spec file
+- These actions belong to `/sf:done`, not to execution
+
 </process>
 
 <output>

package/commands/sf/run.md

@@ -239,7 +239,13 @@ The agent will:
 2. Create atomic commits
 3. Handle deviations
 4. Add Execution Summary to spec
-5. Update STATE.md to "review"
+5. Update STATE.md status to "review"
+
+**After agent returns, verify STATE.md is correct:**
+- Active Specification must still be the SAME spec (not advanced to next)
+- Status must be "review" (not "done" or "draft")
+- Spec must still be in Queue (not moved to Completed)
+- If agent over-advanced the state, revert to: active=SPEC-XXX, status=review, next=/sf:review
 
 ## Step 9.5: Check STATE.md Size and Rotate if Needed
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "specflow-cc",
-  "version": "1.11.0",
+  "version": "1.11.1",
   "description": "Spec-driven development system for Claude Code — quality-first workflow with explicit audit cycles",
   "bin": {
     "specflow-cc": "bin/install.js"