specflow-cc 1.9.3 → 1.9.4

package/CHANGELOG.md

@@ -5,6 +5,24 @@ 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.9.4] - 2026-02-05
+
+### Fixed
+
+- **Spec ID collision bug** — numbering now checks both `specs/` and `archive/` directories
+  - Previously, when all specs were archived, new specs would start from SPEC-001 again
+  - This caused ID collisions with archived specs
+  - Affected files: `spec-creator.md`, `new.md`
+
+### Added
+
+- **State consistency validation** in `/sf:status` (Step 4.5)
+  - Detects orphan specs (files in `specs/` but STATE.md shows "None")
+  - Detects duplicate IDs (same spec in both `specs/` and `archive/`)
+  - Provides actionable warnings with suggested fixes
+
+---
+
 ## [1.9.1] - 2026-02-02
 
 ### Fixed

package/agents/spec-creator.md

@@ -105,13 +105,15 @@ Limit: 1-3 questions maximum. Zero is fine if task is clear or discussion is com
 
 ## Step 4: Generate Spec ID
 
-Find next available SPEC-XXX number:
+Find next available SPEC-XXX number by checking BOTH specs and archive directories:
 
 ```bash
-ls .specflow/specs/SPEC-*.md 2>/dev/null | sort -V | tail -1
+ls .specflow/specs/SPEC-*.md .specflow/archive/SPEC-*.md 2>/dev/null | grep -oP 'SPEC-\K\d+' | sort -n | tail -1
 ```
 
-If no specs exist, start with SPEC-001.
+If no specs exist in either directory, start with SPEC-001.
+
+**Important:** Always check both directories to prevent ID collisions with archived specs.
 
 ## Step 5: Create Specification
 

package/commands/sf/new.md

@@ -176,7 +176,8 @@ Consider `/sf:split SPEC-XXX` to decompose into smaller specs.
 ### Get Next Spec Number
 
 ```bash
-LAST=$(ls .specflow/specs/SPEC-*.md 2>/dev/null | sort -V | tail -1 | grep -oP 'SPEC-\K\d+')
+# Check BOTH specs and archive directories to prevent ID collisions
+LAST=$(ls .specflow/specs/SPEC-*.md .specflow/archive/SPEC-*.md 2>/dev/null | grep -oP 'SPEC-\K\d+' | sort -n | tail -1)
 NEXT=$(printf "%03d" $((${LAST:-0} + 1)))
 echo "SPEC-$NEXT"
 ```

package/commands/sf/status.md

@@ -61,6 +61,38 @@ DONE=$(ls .specflow/archive/SPEC-*.md 2>/dev/null | wc -l)
 TODOS=$(ls .specflow/todos/*.md 2>/dev/null | wc -l)
 ```
 
+## Step 4.5: Validate State Consistency
+
+Check for mismatches between STATE.md and actual files:
+
+```bash
+# Check for orphan specs (exist in specs/ but STATE.md says "None")
+ORPHAN_SPECS=$(ls .specflow/specs/SPEC-*.md 2>/dev/null | head -1)
+
+# Check for duplicate IDs (same spec in both specs/ and archive/)
+for f in .specflow/specs/SPEC-*.md; do
+  [ -f "$f" ] || continue
+  ID=$(basename "$f")
+  [ -f ".specflow/archive/$ID" ] && echo "DUPLICATE: $ID"
+done
+```
+
+**If STATE.md shows "Active Specification: None" but specs exist in specs/:**
+Add warning:
+```
+STATE MISMATCH: Found {N} spec(s) in specs/ but STATE.md shows no active spec.
+Likely cause: STATE.md was not updated after spec creation.
+Run: Read the spec file and manually update STATE.md, or delete orphan spec if duplicate.
+```
+
+**If duplicate IDs found:**
+Add warning:
+```
+DUPLICATE ID: {SPEC-XXX} exists in both specs/ and archive/.
+Likely cause: Spec numbering bug - archive was not checked when generating ID.
+Fix: Rename the spec in specs/ to next available ID.
+```
+
 ## Step 5: Determine Next Action
 
 Based on current status:

package/package.json

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