fix(workflow): prevent specification sign-off from getting stuck

.claude-plugin/marketplace.json

@@ -10,7 +10,7 @@
       "name": "claude-constructor",
       "source": "./plugins/claude-constructor",
       "description": "A workflow automation system that helps Claude Code implement features systematically with built-in planning, validation, and review steps",
-      "version": "1.3.0"
+      "version": "1.3.1"
     }
   ]
 }

package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-constructor",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "A workflow automation plugin for Claude Code",
   "private": true,
   "scripts": {

plugins/claude-constructor/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "claude-constructor",
   "description": "A workflow automation system that helps Claude Code implement features systematically with built-in planning, validation, and review steps",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "author": {
     "name": "Jonas Martinsson & Anders Hassis",
     "url": "https://github.com/Hurblat/claude-constructor/graphs/contributors"

plugins/claude-constructor/commands/specification-sign-off.md

@@ -104,6 +104,8 @@ You MUST follow all workflow steps below, not skipping any step and doing all st
    - Read the state management file ($1)
    - Update `specificationApproved: false` to `specificationApproved: true` in the Workflow Progress section
 
-8. **Add Issue Comment**:
-   - Read the state management file to get the issue key
-   - Use the Skill tool to execute `/create-comment [issue-key] "[specification details and assumptions]" $1`
+8. **Add Issue Comment** (skip if provider is "prompt"):
+   - Read the state management file to get the issue key and provider
+   - If provider is NOT "prompt": Use the Skill tool to execute `/create-comment [issue-key] "[specification details and assumptions]" $1`
+
+9. Specification sign-off is complete