speccrew 0.7.23 → 0.7.24

package/.speccrew/agents/speccrew-task-worker.md

@@ -30,10 +30,18 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
 
 ### When to Pause (ONLY these cases)
 
-1. CHECKPOINT gates defined in workflow (user confirmation required by design)
-2. Ambiguous requirements that genuinely need clarification
-3. Unrecoverable errors that prevent further progress
-4. Security-sensitive operations (e.g., deleting existing files)
+1. **Event blocks with user interaction** (HIGHEST PRIORITY):
+   - `<block type="event" action="user-confirm">` — MUST pause and present prompt to user, wait for explicit confirmation
+   - This applies even in automated dispatch scenarios — user-confirm events override Worker autonomy
+   - FORBIDDEN: Skipping, auto-confirming, or bypassing with reasoning like "automated execution scenario"
+
+2. CHECKPOINT gates defined in workflow (user confirmation required by design)
+
+3. Ambiguous requirements that genuinely need clarification
+
+4. Unrecoverable errors that prevent further progress
+
+5. Security-sensitive operations (e.g., deleting existing files)
 
 ### Batch Execution Behavior
 

package/.speccrew/skills/speccrew-pm-requirement-clarify/SKILL.md

@@ -86,7 +86,10 @@ Applies ISA-95 Stage 1 (Domain Description) for clarification:
 - Manually write JSON files
 - Auto-proceed to Phase 4 (PRD generation) without PM Agent's user confirmation gate
 - Auto-pass sufficiency checks without actual user answers
-- Write checkpoints in this Skill — checkpoints are managed by orchestration layer
+- **Checkpoint management is FORBIDDEN in this Skill**
+  - MUST NOT create, write, or modify `.checkpoints.json` or any checkpoint files
+  - Checkpoint write operations are the responsibility of the orchestration layer (PM Agent)
+  - After this Skill completes, PM Agent writes checkpoints ONLY after user confirmation is received
 
 ### MANDATORY: User Answer Verification Rule
 
@@ -95,6 +98,13 @@ Applies ISA-95 Stage 1 (Domain Description) for clarification:
 - Checkpoint writing is FORBIDDEN in this Skill — checkpoints are managed by the orchestration layer
 - The sufficiency check result is ONLY valid when based on real user-provided answers
 
+### CRITICAL: User Confirmation Event Enforcement
+
+1. **Event Block = Hard Stop**: Each `<block type="event" action="user-confirm">` (E-ROUND-CONFIRM) MUST trigger a pause. Worker MUST NOT proceed until user provides explicit confirmation.
+2. **No "Automated Scenario" Bypass**: Even in automated dispatch mode (speccrew-task-worker), `user-confirm` events override Worker autonomy. These are explicit user interaction gates, NOT internal automation points.
+3. **Template-Based Generation Only**: All clarification question files (`.clarification-questions-round-{N}.md`) MUST be generated using the loaded template (CLARIFICATION-QUESTIONS-TEMPLATE.md) with variable substitution. Freeform generation is FORBIDDEN.
+4. **Template-Based Summary Only**: The `.clarification-summary.md` MUST be generated using CLARIFICATION-SUMMARY-TEMPLATE.md with variable substitution. Freeform generation is FORBIDDEN.
+
 ### CRITICAL: Summary Generation Guard
 
 Worker MUST strictly enforce the following before generating `.clarification-summary.md`:

package/.speccrew/skills/speccrew-pm-requirement-clarify/workflow.agentflow.xml

@@ -99,6 +99,13 @@
       <branch test="${complexity} == 'complex'" name="Complex Mode Clarification">
         <!-- Clarification Loop -->
         <block type="loop" id="L1" condition="sufficiency_checks_passed == false AND round_number <= max_rounds" desc="Clarification rounds until sufficiency">
+          <!-- MANDATORY: Template-based generation rule -->
+          <block type="rule" id="R-TEMPLATE-GENERATION" level="mandatory" desc="Template-based generation is MANDATORY">
+            <field name="text">MANDATORY: Clarification questions MUST be generated by loading the template file and performing variable substitution.</field>
+            <field name="text">FORBIDDEN: Freeform generation, manual writing, or creating clarification files without using the loaded template.</field>
+            <field name="text">The generated file must follow the template structure with all placeholders replaced by actual values.</field>
+          </block>
+
           <!-- Load Question Template -->
           <block type="task" id="B7-load-template" action="read-file" desc="Load clarification questions template">
             <field name="path" value="${skill_path}/templates/CLARIFICATION-QUESTIONS-TEMPLATE.md"/>
@@ -118,6 +125,13 @@
             <field name="output" var="questions_file"/>
           </block>
 
+          <!-- MANDATORY: User confirmation cannot be bypassed -->
+          <block type="rule" id="R-USER-CONFIRM-MANDATORY" level="mandatory" desc="User-confirm events MUST pause Worker execution">
+            <field name="text">MANDATORY: The following user-confirm event is a HARD STOP. Worker MUST pause and present the prompt to user.</field>
+            <field name="text">FORBIDDEN: Skipping, auto-confirming, or bypassing user-confirm events for ANY reason including "automated execution scenario".</field>
+            <field name="text">Worker MUST wait for explicit user response before proceeding to the next block.</field>
+          </block>
+
           <!-- MANDATORY: Wait for user to answer clarification questions -->
           <block type="event" id="E-ROUND-CONFIRM" action="user-confirm" desc="Wait for user to answer clarification questions">
             <field name="prompt">📋 第 ${round_number} 轮澄清问题已生成: ${questions_file}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speccrew",
-  "version": "0.7.23",
+  "version": "0.7.24",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {

package/workspace-template/docs/rules/agentflow-spec.md

@@ -184,6 +184,18 @@ Logging, confirmation, and signaling.
 - `action`: `log` | `confirm` | `signal`
 - `level` (for log): `debug` | `info` | `warn` | `error`
 
+#### User-Confirm Event Execution Rules (MANDATORY)
+
+When a Worker encounters `<block type="event" action="user-confirm">`:
+
+1. **MUST pause execution** — Stop all processing and present the prompt to the user
+2. **CANNOT be skipped or auto-confirmed** — Even if Worker considers the scenario "automated"
+3. **Applies to ALL execution modes** — Including dispatch-to-worker, batch processing, and automated scenarios
+4. **`skippable="false"` is absolute** — When set, no bypass mechanism is permitted under any circumstances
+5. **Variable preservation** — Before pausing, ensure all workflow variables are properly set for resumption
+
+`user-confirm` events represent **explicit user interaction gates** in the workflow. They exist to ensure human oversight at critical decision points and MUST NOT be optimized away.
+
 ### error-handler
 
 Try/catch/finally error handling.