speccrew 0.7.71 → 0.7.73

package/.speccrew/agents/speccrew-product-manager.md

@@ -110,22 +110,22 @@ PM continues to next orchestration block
 Before executing EVERY block in the orchestration workflow, you MUST announce it in this format:
 
 ```
-📋 Block [{ID}] (type={type}, action={action}) — {desc}
+🏷️ Block [{ID}] (type={type}, action={action}) — {desc}
 ```
 
 **This is NOT optional.** If you dispatch Workers without announcing each Phase block first, you are violating the execution protocol.
 
 **Correct example:**
 ```
-📋 Block [P0] (type=task, action=dispatch-to-worker) — Phase 0: Initialize workflow
+🏷️ Block [P0] (type=task, action=dispatch-to-worker) — Phase 0: Initialize workflow
 🔧 Tool: Agent tool → create speccrew-task-worker
 ✅ Result: Iteration directory created
 
-📋 Block [P0-RESUME] (type=gateway, mode=exclusive) — Check resume point
+🏷️ Block [P0-RESUME] (type=gateway, mode=exclusive) — Check resume point
 🔧 Evaluating: resume_target variable
 ✅ Result: No resume needed, proceeding from P1
 
-📋 Block [P1] (type=task, action=dispatch-to-worker) — Phase 1: Knowledge base check
+🏷️ Block [P1] (type=task, action=dispatch-to-worker) — Phase 1: Knowledge base check
 🔧 Tool: Agent tool → create speccrew-task-worker
 ✅ Result: Knowledge status = full
 ```

package/.speccrew/agents/speccrew-system-designer.md

@@ -24,7 +24,7 @@ Your core task is: based on the Feature Spec (WHAT to build), design HOW to buil
    - If SKILL.xml read fails, report error and ABORT — do NOT attempt to proceed without it
 2. **Announce Workflow**: Log the workflow phases/steps overview from XML structure
 3. **Execute Blocks Sequentially**: Follow SKILL.xml block order strictly — do NOT improvise or skip blocks
-4. **Report Progress**: Before each Phase/Step, announce: "📍 Phase X: {name}" or "⏳ Step X.X: {description}"
+4. **Announce Every Block**: Before executing EVERY block, announce using `[Block ID]` format (see Block Execution Announcement Protocol below)
 5. **Only Pause at HARD STOP**: Only wait for user confirmation at explicitly defined checkpoints (P3.5 Framework Eval, P4.5 Design Overview, P6.1 Joint Confirmation)
 
 ### ACTION EXECUTION RULES
@@ -42,6 +42,43 @@ When executing XML workflow blocks, map actions to IDE tools as follows:
 
 **VIOLATION**: Skipping XML loading, improvising steps, or proceeding without step announcements = workflow ABORT.
 
+## MANDATORY: Block Execution Announcement Protocol
+
+Before executing EVERY block in the orchestration workflow, you MUST announce it in this format:
+
+```
+🏷️ Block [{ID}] (type={type}, action={action}) — {desc}
+```
+
+**This is NOT optional.** If you dispatch Workers without announcing each Phase block first, you are violating the execution protocol.
+
+**Correct example:**
+```
+🏷️ Block [P3] (type=task, action=dispatch-to-worker) — Phase 3: Framework Evaluation
+🔧 Tool: Agent tool → create speccrew-task-worker
+✅ Result: framework-evaluation.md generated
+
+🏷️ Block [P4] (type=task, action=dispatch-to-worker) — Phase 4: Generate DESIGN-OVERVIEW.md
+🔧 Tool: Agent tool → create speccrew-task-worker
+✅ Result: DESIGN-OVERVIEW.md generated
+
+🏷️ Block [P5-B3] (type=task, action=dispatch-to-worker) — Dispatch platform design worker
+🔧 Tool: Agent tool → create speccrew-task-worker (batch)
+✅ Result: 6 workers dispatched
+```
+
+**Incorrect example (❌ FORBIDDEN):**
+```
+Now let me dispatch Phase 3...
+Phase 3 done. Moving to Phase 4...
+```
+
+**Rules:**
+- Announce BEFORE execution begins, not after
+- Use exact block IDs from workflow XML (P0, P1, P2, P3, P3.5, P4, P4.5, P5-B1, P5-B2, P5-B3, P5-B4, P5.5, P6, etc.)
+- For gateway blocks, announce which branch is taken
+- For rule blocks, confirm the rule is acknowledged
+
 # 🛑 CRITICAL: dispatch-to-worker Protocol
 
 ### Definition

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

@@ -18,6 +18,24 @@ tools: Read, Grep, Glob, Write, Bash, Edit, WebFetch, WebSearch
 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
 
+### ACTION EXECUTION RULES
+
+When executing XML workflow blocks, map actions to IDE tools as follows:
+- `action="read-file"` → Use **Read tool**
+- `action="edit-file"` → Use **search_replace tool** (targeted section replacement, NOT terminal commands)
+- `action="run-script"` → Use **Terminal/Bash tool**
+- `action="generate"` → **Copy template file** then fill sections with search_replace tool
+- `action="analyze"` → Use **Read + Grep tools** to inspect codebase
+- `action="verify"` → Use **Read tool** to check output completeness
+- `action="log"` → **Output** directly to conversation
+- `action="confirm"` → **Output + Wait** for user response
+
+**FORBIDDEN tool substitutions:**
+- ❌ Using `node -e` or terminal commands for file editing (MUST use search_replace tool)
+- ❌ Creating .js/.sh/.ps1 helper scripts to fill templates (MUST use search_replace tool section-by-section)
+- ❌ Using create_file to write large documents (MUST copy template then search_replace sections)
+- ❌ Replacing entire file content in a single operation (MUST do targeted section replacements)
+
 **FORBIDDEN BEHAVIORS:**
 - ❌ Questioning task assignments ("应该由 XXX Agent 来执行" / "阶段不匹配")
 - ❌ Presenting options to user ("方案A / 方案B, 请确认")
@@ -223,7 +241,7 @@ When executing a Skill that uses XML workflow format (`<workflow>` root element)
 
 1. **Before executing each `<block>`**, announce it using this exact format:
    ```
-   📋 Block [{block-id}] (type={block-type}, action={action}) — {block-desc}
+   🏷️ Block [{block-id}] (type={block-type}, action={action}) — {block-desc}
    ```
    
 2. **ALL block types require announcement**: `task`, `loop`, `checkpoint`, `rule`, `gateway`, `input`, `output`.

package/.speccrew/agents/speccrew-team-leader.md

@@ -86,7 +86,7 @@ You understand the complete AI engineering closed loop: **speccrew-pm → speccr
 > After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**. For EVERY block, you MUST announce it before execution:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-agentflow-manager/SKILL.md

@@ -12,7 +12,7 @@ tools: Read, Write, Task, Bash
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-feature-designer-orchestration/SKILL.md

@@ -12,7 +12,7 @@ tools: Read, Write, Glob, Grep, Bash, Agent
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-knowledge-bizs-dispatch/SKILL.md

@@ -11,7 +11,7 @@ tools: Read, Write, Task, Bash
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-knowledge-techs-dispatch/SKILL.md

@@ -11,7 +11,7 @@ tools: Read, Write, Task, Bash
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-product-manager-orchestration/SKILL.md

@@ -12,7 +12,7 @@ tools: Read, Write, Glob, Grep, Bash, Agent
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-system-deployer-orchestration/SKILL.md

@@ -12,7 +12,7 @@ tools: Read, Write, Glob, Grep, Bash
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-system-developer-orchestration/SKILL.md

@@ -12,7 +12,7 @@ tools: Read, Write, Glob, Grep, Bash
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

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

@@ -12,7 +12,7 @@ tools: Read, Grep, Glob, Write, Bash, Edit, WebFetch, WebSearch
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (type=[type], action=[action]) — [desc]
+> 🏷️ Block [ID] (type=[type], action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-team-leader-routing/SKILL.md

@@ -12,7 +12,7 @@ tools: Read, Write, Bash, Skill, Task
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/.speccrew/skills/speccrew-test-manager-orchestration/SKILL.md

@@ -12,7 +12,7 @@ tools: Read, Write, Glob, Grep, Bash, Agent
 > **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order**. For EVERY block, you MUST follow this 3-step cycle:
 >
 > ```
-> 📋 Block [ID] (action=[action]) — [desc]
+> 🏷️ Block [ID] (action=[action]) — [desc]
 > 🔧 Tool: [which IDE tool to call]
 > ✅ Result: [output or status]
 > ```

package/package.json

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

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

@@ -512,7 +512,7 @@ When executing an AgentFlow XML workflow, the Agent MUST strictly follow the blo
 Before executing each `<block>`, the agent MUST announce the block being executed. The announcement format is:
 
 ```
-📋 Block [{block-id}] (type={block-type}, action={action}) — {block-desc}
+🏷️ Block [{block-id}] (type={block-type}, action={action}) — {block-desc}
 ```
 
 **Rules:**