speccrew 0.7.66 → 0.7.68

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

@@ -4,6 +4,25 @@ description: Generic task execution Worker. Invoked in parallel by other Agents
 tools: Read, Grep, Glob, Write, Bash, Edit, WebFetch, WebSearch
 ---
 
+## EXECUTION PROTOCOL
+
+**Worker MUST follow this protocol for EVERY task execution:**
+
+1. **Load Skill XML First**: Read the assigned skill's SKILL.xml completely before any business logic
+2. **Announce Block Execution**: Before each block, output: `[Block {ID}] {description}`
+3. **Execute Blocks Sequentially**: Follow SKILL.xml block order strictly — do NOT improvise, skip, or reorder blocks
+4. **Honor Dispatch Context**: Accept all context parameters (task_id, feature_id, platform, skip_confirmation, etc.) as authoritative — do NOT question or validate them
+5. **Report Completion**: Output structured completion report with status, task_id, output_files
+
+**FORBIDDEN BEHAVIORS:**
+- ❌ Questioning task assignments ("应该由 XXX Agent 来执行" / "阶段不匹配")
+- ❌ Presenting options to user ("方案A / 方案B, 请确认")
+- ❌ Executing based on SKILL.md text instead of SKILL.xml blocks
+- ❌ Creating helper scripts or temporary files
+- ❌ Modifying dispatch context parameters
+
+**VIOLATION**: Any of the above = task FAILED, report error immediately.
+
 # Role Definition
 
 You are a generic task execution Worker, focused on executing a single task. Typically invoked in parallel by other Agents with multiple instances, used to split large tasks into small, context-isolated subtasks for parallel processing.

package/.speccrew/skills/speccrew-system-designer-orchestration/SKILL.xml

@@ -92,15 +92,17 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 0: Stage Gate & Resume ========== -->
   <sequence name="Phase 0: Stage Gate &amp; Resume">
     <block type="event" id="P0-ANNOUNCE" action="log" desc="Phase 0 announcement">
-      <field name="message">📍 Phase 0: Stage Gate &amp; Resume (阶段门控与恢复)
-├── Step 0.1: 验证上游阶段完成状态
-├── Step 0.2: 检查恢复状态
-├── Step 0.3: 检查调度进度恢复
-└── Step 0.4: 同步恢复(如有需要)</field>
+      <field name="message">📍 [Phase 0] Stage Gate &amp; Resume (阶段门控与恢复)
+├── [P0-B1] 验证上游阶段完成状态
+├── [P0-B3] 检查恢复状态
+├── [P0-B4] 检查调度进度恢复
+└── [P0-R1] 同步恢复(如有需要)</field>
     </block>
 
     <!-- Step 0.1: Verify Upstream Completion -->
-    <block type="event" id="P0-S1-LOG" action="log" desc="Step 0.1: 验证上游阶段完成状态"/>
+    <block type="event" id="P0-S1-LOG" action="log" desc="Step 0.1: 验证上游阶段完成状态">
+      <field name="message">[Block P0-B1] 验证上游阶段完成状态</field>
+    </block>
     <block type="task" id="P0-B1" action="run-script" status="pending"
            desc="Read WORKFLOW-PROGRESS.json overview">
       <field name="command">node ${update_progress_script} read --file ${iterations_dir}/${current_iteration}/WORKFLOW-PROGRESS.json --overview</field>
@@ -123,7 +125,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 0.2: Check Resume State -->
-    <block type="event" id="P0-S2-LOG" action="log" desc="Step 0.2: 检查恢复状态"/>
+    <block type="event" id="P0-S2-LOG" action="log" desc="Step 0.2: 检查恢复状态">
+      <field name="message">[Block P0-B3] 检查恢复状态</field>
+    </block>
     <block type="task" id="P0-B3" action="run-script" status="pending"
            desc="Read checkpoints for resume state">
       <field name="command">node ${update_progress_script} read --file ${iterations_dir}/${current_iteration}/03.system-design/.checkpoints.json --checkpoints</field>
@@ -131,7 +135,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 0.3: Check Dispatch Resume -->
-    <block type="event" id="P0-S3-LOG" action="log" desc="Step 0.3: 检查调度进度恢复"/>
+    <block type="event" id="P0-S3-LOG" action="log" desc="Step 0.3: 检查调度进度恢复">
+      <field name="message">[Block P0-B4] 检查调度进度恢复</field>
+    </block>
     <block type="task" id="P0-B4" action="run-script" status="pending"
            desc="Read dispatch progress summary">
       <field name="command">node ${update_progress_script} read --file ${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json --summary</field>
@@ -151,11 +157,13 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 0.5: IDE Directory Detection ========== -->
   <sequence name="Phase 0.5: IDE Directory Detection">
     <block type="event" id="P05-ANNOUNCE" action="log" desc="Phase 0.5 announcement">
-      <field name="message">📍 Phase 0.5: IDE Directory Detection (IDE目录检测)
-└── Step 0.5.1: 检测IDE目录和技能可用性</field>
+      <field name="message">📍 [Phase 0.5] IDE Directory Detection (IDE目录检测)
+└── [P05-B1] 检测IDE目录和技能可用性</field>
     </block>
 
-    <block type="event" id="P05-S1-LOG" action="log" desc="Step 0.5.1: 检测IDE目录和技能"/>
+    <block type="event" id="P05-S1-LOG" action="log" desc="Step 0.5.1: 检测IDE目录和技能">
+      <field name="message">[Block P05-B1] 检测IDE目录和技能可用性</field>
+    </block>
     <block type="task" id="P05-B1" action="read-file" status="pending"
            desc="Detect IDE directory and skills">
       <field name="path">${workspace_path}/.qoder/skills</field>
@@ -186,11 +194,11 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 1: Preparation ========== -->
   <sequence name="Phase 1: Preparation">
     <block type="event" id="P1-ANNOUNCE" action="log" desc="Phase 1 announcement">
-      <field name="message">📍 Phase 1: Preparation (准备阶段)
-├── Step 1.1: 加载Feature Registry
-├── Step 1.2: 验证文件存在性
-├── Step 1.4: 展示设计范围摘要
-└── Step 1.5: 验证准备完成</field>
+      <field name="message">📍 [Phase 1] Preparation (准备阶段)
+├── [P1-B1] 加载Feature Registry
+├── [P1-G1] 验证文件存在性
+├── [P1-E4] 展示设计范围摘要
+└── [P1-CP1] 验证准备完成</field>
     </block>
 
     <block type="rule" id="P1-R1" level="forbidden" desc="Phase 1 Mandatory Constraints">
@@ -200,7 +208,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 1.1: Load Feature Registry -->
-    <block type="event" id="P1-S1-LOG" action="log" desc="Step 1.1: 加载Feature Registry"/>
+    <block type="event" id="P1-S1-LOG" action="log" desc="Step 1.1: 加载Feature Registry">
+      <field name="message">[Block P1-B1] 加载Feature Registry</field>
+    </block>
     <block type="task" id="P1-B1" action="read-file" status="pending"
            desc="Load Feature Registry from .prd-feature-list.json">
       <field name="path">${iterations_dir}/${current_iteration}/01.product-requirement/.prd-feature-list.json</field>
@@ -208,7 +218,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 1.2: Verify File Existence -->
-    <block type="event" id="P1-S2-LOG" action="log" desc="Step 1.2: 验证文件存在性"/>
+    <block type="event" id="P1-S2-LOG" action="log" desc="Step 1.2: 验证文件存在性">
+      <field name="message">[Block P1-G1] 验证文件存在性</field>
+    </block>
     <block type="gateway" id="P1-G1" mode="exclusive" desc="Verify Feature Spec and API Contract files exist">
       <branch test="${feature_registry.files} all_exist" name="All Files Exist">
         <block type="event" id="P1-E1" action="log" desc="Report files verified"/>
@@ -222,14 +234,18 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 1.4: Present Design Scope -->
-    <block type="event" id="P1-S4-LOG" action="log" desc="Step 1.4: 展示设计范围摘要"/>
+    <block type="event" id="P1-S4-LOG" action="log" desc="Step 1.4: 展示设计范围摘要">
+      <field name="message">[Block P1-E4] 展示设计范围摘要</field>
+    </block>
     <block type="event" id="P1-E4" action="log" desc="Display Design Scope Summary">
       <field name="template">design-scope-summary</field>
       <field name="data" value="${feature_registry}"/>
     </block>
 
     <!-- Step 1.5: Preparation Validation -->
-    <block type="event" id="P1-S5-LOG" action="log" desc="Step 1.5: 验证准备完成"/>
+    <block type="event" id="P1-S5-LOG" action="log" desc="Step 1.5: 验证准备完成">
+      <field name="message">[Block P1-CP1] 验证准备完成</field>
+    </block>
     <block type="checkpoint" id="P1-CP1" name="preparation_validated" desc="Preparation validation gate">
       <field name="conditions">feature_registry_exists, files_verified, scope_presented</field>
     </block>
@@ -238,9 +254,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 2: Resource Verification ========== -->
   <sequence name="Phase 2: Resource Verification">
     <block type="event" id="P2-ANNOUNCE" action="log" desc="Phase 2 announcement">
-      <field name="message">📍 Phase 2: Resource Verification (资源验证)
-├── Step 2.1: 验证技术知识库
-└── Step 2.2: 准备调度参数</field>
+      <field name="message">📍 [Phase 2] Resource Verification (资源验证)
+├── [P2-B1] 验证技术知识库
+└── [P2-E4] 准备调度参数</field>
     </block>
 
     <block type="rule" id="P2-R1" level="forbidden" desc="Phase 2 Mandatory Constraints">
@@ -251,7 +267,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 2.1: Verify Techs Knowledge Base -->
-    <block type="event" id="P2-S1-LOG" action="log" desc="Step 2.1: 验证技术知识库"/>
+    <block type="event" id="P2-S1-LOG" action="log" desc="Step 2.1: 验证技术知识库">
+      <field name="message">[Block P2-B1] 验证技术知识库</field>
+    </block>
     <block type="task" id="P2-B1" action="read-file" status="pending"
            desc="Check techs-manifest.json exists">
       <field name="path">${workspace_path}/knowledges/techs/techs-manifest.json</field>
@@ -271,7 +289,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 2.2: Prepare Dispatch Parameters -->
-    <block type="event" id="P2-S2-LOG" action="log" desc="Step 2.2: 准备调度参数"/>
+    <block type="event" id="P2-S2-LOG" action="log" desc="Step 2.2: 准备调度参数">
+      <field name="message">[Block P2-E4] 准备调度参数</field>
+    </block>
     <block type="event" id="P2-E4" action="log" desc="Build dispatch parameter template">
       <field name="template">build-dispatch-params</field>
       <field name="output" var="dispatch_params"/>
@@ -281,11 +301,11 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 3: Framework Evaluation (HARD STOP) ========== -->
   <sequence name="Phase 3: Framework Evaluation">
     <block type="event" id="P3-ANNOUNCE" action="log" desc="Phase 3 announcement">
-      <field name="message">📍 Phase 3: Framework Evaluation (框架评估) ⛔ HARD STOP
-├── Step 3.1: 派发Worker执行框架评估
-├── Step 3.2: 等待Worker完成
-├── Step 3.3: 验证输出
-└── Step 3.5: 用户确认 ⛔</field>
+      <field name="message">📍 [Phase 3] Framework Evaluation (框架评估) ⛔ HARD STOP
+├── [P3-B1] 派发Worker执行框架评估
+├── [P3-GW1] 等待Worker完成
+├── [P3-B2] 验证输出
+└── [P3-E4] 用户确认 ⛔</field>
     </block>
 
     <block type="rule" id="P3-R0" level="forbidden" desc="Phase 3 Worker Dispatch Enforcement">
@@ -303,7 +323,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 3.1: Dispatch Worker Agent for Framework Evaluation -->
-    <block type="event" id="P3-S1-LOG" action="log" desc="Step 3.1: 派发Worker执行框架评估"/>
+    <block type="event" id="P3-S1-LOG" action="log" desc="Step 3.1: 派发Worker执行框架评估">
+      <field name="message">[Block P3-B1] 派发Worker执行框架评估</field>
+    </block>
     <block type="task" id="P3-B1" action="dispatch-to-worker" status="pending"
            desc="Dispatch single worker agent for framework evaluation. Use /speccrew-task-worker agent, NOT Skill tool">
       <field name="agent">speccrew-task-worker</field>
@@ -322,14 +344,18 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 3.2: Wait for Worker Completion -->
-    <block type="event" id="P3-S2-LOG" action="log" desc="Step 3.2: 等待框架评估Worker完成"/>
+    <block type="event" id="P3-S2-LOG" action="log" desc="Step 3.2: 等待框架评估Worker完成">
+      <field name="message">[Block P3-GW1] 等待Worker完成</field>
+    </block>
     <block type="gateway" id="P3-GW1" mode="wait" desc="Wait for framework evaluation worker to complete">
       <field name="wait_for">P3-B1</field>
       <field name="timeout">600</field>
     </block>
 
     <!-- Step 3.3: Validate Worker Output -->
-    <block type="event" id="P3-S3-LOG" action="log" desc="Step 3.3: 验证框架评估输出"/>
+    <block type="event" id="P3-S3-LOG" action="log" desc="Step 3.3: 验证框架评估输出">
+      <field name="message">[Block P3-B2] 验证输出</field>
+    </block>
     <block type="task" id="P3-B2" action="read-file" status="pending"
            desc="Verify framework-evaluation.md was generated">
       <field name="path">${iterations_dir}/${current_iteration}/03.system-design/framework-evaluation.md</field>
@@ -350,7 +376,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 3.5: User Confirmation (HARD STOP) -->
-    <block type="event" id="P3-S5-LOG" action="log" desc="Step 3.5: ⛔ 用户确认框架评估结果"/>
+    <block type="event" id="P3-S5-LOG" action="log" desc="Step 3.5: ⛔ 用户确认框架评估结果">
+      <field name="message">[Block P3-E4] 用户确认</field>
+    </block>
     <block type="event" id="P3-E4" action="confirm" desc="Request user confirmation for framework decisions">
       <field name="prompt">🛑 FRAMEWORK EVALUATION — AWAITING CONFIRMATION. Do you approve these framework decisions? (确认/修改/取消)</field>
       <field name="template">framework-evaluation-summary</field>
@@ -377,11 +405,11 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 4: Generate DESIGN-OVERVIEW.md (WORKER-DISPATCH) ========== -->
   <sequence name="Phase 4: Generate DESIGN-OVERVIEW.md (WORKER-DISPATCH)">
     <block type="event" id="P4-ANNOUNCE" action="log" desc="Phase 4 announcement">
-      <field name="message">📍 Phase 4: Design Overview (设计概览) ⛔ HARD STOP
-├── Step 4.1: 派发Worker生成DESIGN-OVERVIEW.md
-├── Step 4.2: 等待Worker完成
-├── Step 4.3: 验证输出
-└── Step 4.5: 用户确认 ⛔</field>
+      <field name="message">📍 [Phase 4] Design Overview (设计概览) ⛔ HARD STOP
+├── [P4-B1] 派发Worker生成DESIGN-OVERVIEW.md
+├── [P4-GW1] 等待Worker完成
+├── [P4-B2] 验证输出
+└── [P4-HS1] 用户确认 ⛔</field>
     </block>
 
     <block type="rule" id="P4-R0" level="forbidden" desc="Phase 4 Worker Dispatch Enforcement">
@@ -391,7 +419,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
       <field name="text">If worker dispatch fails, ABORT — do NOT fallback to inline generation</field>
     </block>
 
-    <block type="event" id="P4-S1-LOG" action="log" desc="Step 4.1: 派发Worker生成DESIGN-OVERVIEW.md"/>
+    <block type="event" id="P4-S1-LOG" action="log" desc="Step 4.1: 派发Worker生成DESIGN-OVERVIEW.md">
+      <field name="message">[Block P4-B1] 派发Worker生成DESIGN-OVERVIEW.md</field>
+    </block>
     <block type="task" id="P4-B1" action="dispatch-to-worker" status="pending"
            desc="Dispatch single worker agent for design overview generation. Use Agent tool, NOT Skill tool.">
       <field name="agent">speccrew-task-worker</field>
@@ -408,13 +438,17 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
       <field name="note">Worker receives ALL context above and generates DESIGN-OVERVIEW.md. Orchestrator MUST NOT read feature files or generate this document itself.</field>
     </block>
 
-    <block type="event" id="P4-S2-LOG" action="log" desc="Step 4.2: 等待设计概览Worker完成"/>
+    <block type="event" id="P4-S2-LOG" action="log" desc="Step 4.2: 等待设计概览Worker完成">
+      <field name="message">[Block P4-GW1] 等待Worker完成</field>
+    </block>
     <block type="gateway" id="P4-GW1" mode="wait" desc="Wait for design overview worker to complete">
       <field name="wait_for">P4-B1</field>
       <field name="timeout">300</field>
     </block>
 
-    <block type="event" id="P4-S3-LOG" action="log" desc="Step 4.3: 验证DESIGN-OVERVIEW.md输出"/>
+    <block type="event" id="P4-S3-LOG" action="log" desc="Step 4.3: 验证DESIGN-OVERVIEW.md输出">
+      <field name="message">[Block P4-B2] 验证输出</field>
+    </block>
     <block type="task" id="P4-B2" action="read-file" status="pending"
            desc="Verify DESIGN-OVERVIEW.md was generated by worker">
       <field name="path">${iterations_dir}/${current_iteration}/03.system-design/DESIGN-OVERVIEW.md</field>
@@ -427,7 +461,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Phase 4.5: HARD STOP — User must confirm DESIGN-OVERVIEW.md -->
-    <block type="event" id="P4-S5-LOG" action="log" desc="Step 4.5: ⛔ 用户确认DESIGN-OVERVIEW.md"/>
+    <block type="event" id="P4-S5-LOG" action="log" desc="Step 4.5: ⛔ 用户确认DESIGN-OVERVIEW.md">
+      <field name="message">[Block P4-HS1] 用户确认</field>
+    </block>
     <block type="rule" id="P4-HS1" level="mandatory" desc="HARD STOP — DESIGN-OVERVIEW.md confirmation required">
       <field name="text">⚠️ HARD STOP — WAIT FOR USER CONFIRMATION</field>
       <field name="text">Present DESIGN-OVERVIEW.md summary to user (feature count, platform count, matrix entries, key sections)</field>
@@ -440,12 +476,12 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 5: Dispatch Per-Platform Skills ========== -->
   <sequence name="Phase 5: Dispatch Per-Platform Skills">
     <block type="event" id="P5-ANNOUNCE" action="log" desc="Phase 5 announcement">
-      <field name="message">📍 Phase 5: Platform Dispatch (平台调度)
-├── Step 5.1: 确定平台类型
-├── Step 5.2: 初始化调度进度
-├── Step 5.3-5.4: 批量派发Worker (每批次最多6个并行)
-├── Step 5.5: 生成平台INDEX.md (Worker派发)
-└── Step 5.6: 错误处理</field>
+      <field name="message">📍 [Phase 5] Platform Dispatch (平台调度)
+├── [P5-E1] 确定平台类型
+├── [P5-B1] 初始化调度进度
+├── [P5-G1] 批量派发Worker (每批次最多6个并行)
+├── [P5-IDX-R1] 生成平台INDEX.md (Worker派发)
+└── [P5-B5] 错误处理</field>
     </block>
 
     <block type="rule" id="P5-R1" level="mandatory" desc="Worker Enforcement Rules">
@@ -456,21 +492,27 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 5.1: Determine Platform Types -->
-    <block type="event" id="P5-S1-LOG" action="log" desc="Step 5.1: 确定平台类型映射"/>
+    <block type="event" id="P5-S1-LOG" action="log" desc="Step 5.1: 确定平台类型映射">
+      <field name="message">[Block P5-E1] 确定平台类型</field>
+    </block>
     <block type="event" id="P5-E1" action="log" desc="Map platform types to skills">
       <field name="template">platform-skill-mapping</field>
       <field name="output" var="platform_skill_map"/>
     </block>
 
     <!-- Step 5.2: Initialize DISPATCH-PROGRESS.json -->
-    <block type="event" id="P5-S2-LOG" action="log" desc="Step 5.2: 初始化调度进度"/>
+    <block type="event" id="P5-S2-LOG" action="log" desc="Step 5.2: 初始化调度进度">
+      <field name="message">[Block P5-B1] 初始化调度进度</field>
+    </block>
     <block type="task" id="P5-B1" action="run-script" status="pending"
            desc="Initialize dispatch progress with task list">
       <field name="command">node ${update_progress_script} init --file ${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json --stage 03_system_design --tasks-file ${iterations_dir}/${current_iteration}/03.system-design/.tasks-temp.json</field>
     </block>
 
     <!-- Step 5.3/5.4: Dispatch Decision -->
-    <block type="event" id="P5-S3-LOG" action="log" desc="Step 5.3: 确定调度模式(单平台直接/多平台Worker派发)"/>
+    <block type="event" id="P5-S3-LOG" action="log" desc="Step 5.3: 确定调度模式(单平台直接/多平台Worker派发)">
+      <field name="message">[Block P5-G1] 确定调度模式(单平台直接/多平台Worker派发)</field>
+    </block>
     <block type="gateway" id="P5-G1" mode="exclusive" desc="Determine dispatch mode">
       <branch test="${feature_count} == 1 AND ${platform_count} == 1" name="Single Feature Single Platform">
         <!-- Direct skill invocation allowed -->
@@ -506,7 +548,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
         </block>
 
         <!-- Compute batch plan from dispatch_tasks_matrix -->
-        <block type="event" id="P5-S4-LOG" action="log" desc="Step 5.4: 计算批量调度计划"/>
+        <block type="event" id="P5-S4-LOG" action="log" desc="Step 5.4: 计算批量调度计划">
+          <field name="message">[Block P5-B4-BATCH] 计算批量调度计划</field>
+        </block>
         <block type="task" id="P5-B4-BATCH" action="compute-batches" status="pending"
                desc="Calculate batch plan from Feature×Platform matrix">
           <field name="items" value="${dispatch_tasks_matrix}"/>
@@ -583,7 +627,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     <!-- Use when orchestrator needs to batch-update multiple task statuses at once -->
 
     <!-- Phase 5.5: Generate Platform INDEX.md (WORKER-DISPATCH) -->
-    <block type="event" id="P5-S5-LOG" action="log" desc="Step 5.5: 派发Worker生成各平台INDEX.md"/>
+    <block type="event" id="P5-S5-LOG" action="log" desc="Step 5.5: 派发Worker生成各平台INDEX.md">
+      <field name="message">[Block P5-IDX-R1] 生成平台INDEX.md (Worker派发)</field>
+    </block>
     <block type="rule" id="P5-IDX-R1" level="mandatory" desc="INDEX.md Generation via Worker Dispatch">
       <field name="text">
         After ALL Feature×Platform workers complete, dispatch ONE worker per platform to generate INDEX.md.
@@ -615,7 +661,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     <block type="gateway" id="P5-IDX-GW1" mode="wait" desc="Wait for all INDEX.md workers to complete"/>
 
     <!-- Step 5.5: Read final dispatch progress -->
-    <block type="event" id="P5-S6-LOG" action="log" desc="Step 5.6: 读取最终调度进度并检查错误"/>
+    <block type="event" id="P5-S6-LOG" action="log" desc="Step 5.6: 读取最终调度进度并检查错误">
+      <field name="message">[Block P5-B5] 错误处理</field>
+    </block>
     <block type="task" id="P5-B5" action="run-script" status="pending"
            desc="Read final dispatch progress summary">
       <field name="command">node "${update_progress_script}" read --file "${iterations_dir}/${current_iteration}/03.system-design/DISPATCH-PROGRESS.json" --summary</field>
@@ -639,21 +687,25 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
   <!-- ========== Phase 6: Joint Confirmation (HARD STOP) ========== -->
   <sequence name="Phase 6: Joint Confirmation">
     <block type="event" id="P6-ANNOUNCE" action="log" desc="Phase 6 announcement">
-      <field name="message">📍 Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
-├── Step 6.1: 展示设计文档摘要
-├── Step 6.2: 用户确认 ⛔
-└── Step 6.3: 更新检查点</field>
+      <field name="message">📍 [Phase 6] Joint Confirmation (联合确认) ⛔ HARD STOP
+├── [P6-E1] 展示设计文档摘要
+├── [P6-E2] 用户确认 ⛔
+└── [P6-B1] 更新检查点</field>
     </block>
 
     <!-- Step 6.1: Present summary by Feature ID -->
-    <block type="event" id="P6-S1-LOG" action="log" desc="Step 6.1: 展示设计文档摘要"/>
+    <block type="event" id="P6-S1-LOG" action="log" desc="Step 6.1: 展示设计文档摘要">
+      <field name="message">[Block P6-E1] 展示设计文档摘要</field>
+    </block>
     <block type="event" id="P6-E1" action="log" desc="Display design documents summary by Feature">
       <field name="template">design-documents-summary</field>
       <field name="data" value="${dispatch_progress}"/>
     </block>
 
     <!-- Step 6.2: User Confirmation (HARD STOP) -->
-    <block type="event" id="P6-S2-LOG" action="log" desc="Step 6.2: ⛔ 用户联合确认"/>
+    <block type="event" id="P6-S2-LOG" action="log" desc="Step 6.2: ⛔ 用户联合确认">
+      <field name="message">[Block P6-E2] 用户确认</field>
+    </block>
     <block type="event" id="P6-E2" action="confirm" desc="Request joint confirmation">
       <field name="prompt">🛑 JOINT CONFIRMATION — AWAITING USER REVIEW. Please review all design documents. (确认/修改/取消)</field>
     </block>
@@ -671,7 +723,9 @@ Phase 6: Joint Confirmation (联合确认) ⛔ HARD STOP
     </block>
 
     <!-- Step 6.3: Update Checkpoints on Confirmation -->
-    <block type="event" id="P6-S3-LOG" action="log" desc="Step 6.3: 更新检查点和工作流状态"/>
+    <block type="event" id="P6-S3-LOG" action="log" desc="Step 6.3: 更新检查点和工作流状态">
+      <field name="message">[Block P6-B1] 更新检查点</field>
+    </block>
     <block type="task" id="P6-B1" action="run-script" status="pending"
            desc="Write framework_evaluation checkpoint">
       <field name="command">node ${update_progress_script} write-checkpoint --file ${iterations_dir}/${current_iteration}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint framework_evaluation --passed true</field>

package/.speccrew/skills/speccrew-task-worker-execution/SKILL.xml

@@ -137,17 +137,17 @@
             
       <!-- MANDATORY: Load XML Workflow Definition -->
       <block type="rule" id="R-WORKFLOW-FIRST" level="mandatory" desc="XML workflow is the authoritative execution definition">
-        <field name="text">MANDATORY: workflow.agentflow.xml is the AUTHORITATIVE execution definition. SKILL.md is supplementary context only.</field>
-        <field name="text">Worker MUST read workflow.agentflow.xml BEFORE starting any task execution.</field>
-        <field name="text">Worker MUST execute ONLY the blocks defined in workflow.agentflow.xml, in sequential document order.</field>
+        <field name="text">MANDATORY: SKILL.xml is the AUTHORITATIVE execution definition. SKILL.md is supplementary context only.</field>
+        <field name="text">Worker MUST read SKILL.xml BEFORE starting any task execution.</field>
+        <field name="text">Worker MUST execute ONLY the blocks defined in SKILL.xml, in sequential document order.</field>
         <field name="text">FORBIDDEN: Executing tasks based solely on SKILL.md description without reading the XML workflow.</field>
       </block>
       
       <block type="task" id="T6b" action="read-file" desc="MANDATORY: Read XML workflow definition">
-        <field name="path">${skill_path}/workflow.agentflow.xml</field>
+        <field name="path">${skill_path}/SKILL.xml</field>
         <field name="output" var="skill_workflow_xml"/>
       </block>
-      <block type="event" id="E8b" action="log" desc="Loaded XML workflow">📄 Loaded workflow: ${skill_path}/workflow.agentflow.xml — This is the AUTHORITATIVE execution plan. Execute blocks in document order.</block>
+      <block type="event" id="E8b" action="log" desc="Loaded XML workflow">📄 Loaded workflow: ${skill_path}/SKILL.xml — This is the AUTHORITATIVE execution plan. Execute blocks in document order.</block>
             
       <!-- 加载 AgentFlow 规范 -->
       <block type="task" id="T7" action="read-file" desc="读取 AgentFlow 规范">

package/package.json

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