@leeovery/claude-technical-workflows 2.0.33 → 2.0.35

package/commands/workflow/start-specification.md

@@ -333,7 +333,7 @@ Coupling: {explanation}
 
 How would you like to proceed?
 
-1. **Combine as recommended** - I'll ask which grouping to start with
+1. **Proceed as recommended** - I'll ask which to start with
 2. **Combine differently** - Tell me your preferred groupings
 3. **Single specification** - Consolidate ALL into one unified spec
 4. **Individual specifications** - Create 1:1 specs (I'll ask which to start)
@@ -351,16 +351,23 @@ How would you like to proceed?
 
 Based on user's choice from Step 7:
 
-#### If "Combine as recommended"
+#### If "Proceed as recommended"
 
 ```
-Which grouping would you like to start with?
+Which would you like to start with?
 
+Grouped:
 1. {Grouping Name A} - {N} discussions
 2. {Grouping Name B} - {N} discussions (specification exists)
 3. {Grouping Name C} - {N} discussions
+
+Independent:
+4. {topic-f} - standalone
+5. {topic-g} - standalone
 ```
 
+List ALL items from the analysis: grouped specifications first, then independent discussions. Number them consecutively.
+
 **STOP.** Wait for user to pick a number, then proceed to **Step 9**.
 
 #### If "Combine differently"
@@ -506,7 +513,7 @@ Before invoking the specification skill:
 2. Any constraints or changes since the discussion(s) concluded?
 3. Are there existing partial implementations or related documentation I should review?
 
-(Press enter to skip if none)
+(Say 'none' or 'continue' if nothing to add)
 ```
 
 **STOP.** Wait for user response.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leeovery/claude-technical-workflows",
-  "version": "2.0.33",
+  "version": "2.0.35",
   "description": "Technical workflow skills & commands for Claude Code",
   "license": "MIT",
   "author": "Lee Overy <me@leeovery.com>",

package/scripts/specification-discovery.sh

@@ -15,15 +15,31 @@ SPEC_DIR="docs/workflow/specification"
 CACHE_FILE="docs/workflow/.cache/discussion-consolidation-analysis.md"
 
 # Helper: Extract a frontmatter field value from a file
+# Supports both YAML frontmatter and markdown format (**Field**: Value)
 # Usage: extract_field <file> <field_name>
 extract_field() {
     local file="$1"
     local field="$2"
-    # Read until --- (end of frontmatter), find field, extract value
-    # Use grep -m1 and || true to handle no match gracefully
-    sed -n '/^---$/,/^---$/p' "$file" 2>/dev/null | \
-        grep -m1 "^${field}:" | \
-        sed "s/^${field}:[[:space:]]*//" || true
+    local value=""
+
+    # Try YAML frontmatter first (only if file starts with ---)
+    if head -1 "$file" 2>/dev/null | grep -q "^---$"; then
+        value=$(sed -n '2,/^---$/p' "$file" 2>/dev/null | \
+            grep -m1 "^${field}:" | \
+            sed "s/^${field}:[[:space:]]*//" || true)
+    fi
+
+    # If empty, try markdown format: **Field**: Value
+    # Only search the header (before first ## heading) to avoid body matches
+    if [ -z "$value" ]; then
+        value=$(awk '/^## /{exit} {print}' "$file" 2>/dev/null | \
+            grep -i -m1 "^\*\*${field}\*\*:" | \
+            sed -E "s/^\*\*[^*]+\*\*:[[:space:]]*//" || true)
+        # Normalize to lowercase for consistency
+        value=$(echo "$value" | tr '[:upper:]' '[:lower:]')
+    fi
+
+    echo "$value"
 }
 
 # Helper: Extract array field from frontmatter (returns space-separated values)