speccrew 0.6.50 → 0.6.51

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

@@ -76,6 +76,8 @@ You understand the complete AI engineering closed loop: **speccrew-pm → speccr
 # Workflow (XML Block Definition)
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
+>
+> After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**. Every `<block type="task">` is a literal tool-call instruction — use the `action` attribute to determine which IDE tool to invoke, and pass the `<field name="command">` or `<field name="skill">` value **exactly as written**. Do NOT interpret the workflow as a goal description or improvise your own approach.
 
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>

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

@@ -99,6 +99,8 @@ Stage 4: System Summary
 ## XML Workflow Definition
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
+>
+> After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**. Every `<block type="task">` is a literal tool-call instruction — use the `action` attribute to determine which IDE tool to invoke, and pass the `<field name="command">` or `<field name="skill">` value **exactly as written**. Do NOT interpret the workflow as a goal description or improvise your own approach.
 
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>

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

@@ -119,6 +119,8 @@ Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized pl
 ## XML Workflow Definition
 
 > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
+>
+> After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**. Every `<block type="task">` is a literal tool-call instruction — use the `action` attribute to determine which IDE tool to invoke, and pass the `<field name="command">` or `<field name="skill">` value **exactly as written**. Do NOT interpret the workflow as a goal description or improvise your own approach.
 
 ```xml
 <?xml version="1.0" encoding="UTF-8"?>

package/package.json

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

package/workspace-template/docs/rules/xml-workflow-spec.md

@@ -393,9 +393,10 @@ When executing `<block type="task">` blocks, the `action` attribute determines w
 ## Execution Rules
 
 1. **NEVER skip a block** — execute every block in document order
-2. **Read `rule` blocks as constraints** — check them continuously during execution
-3. **`checkpoint` blocks** = persist progress before continuing
-4. **`gateway mode="exclusive"`** = only execute the first matching branch
-5. **`loop parallel="true"`** = dispatch all iterations concurrently
-6. **`rule level="forbidden"`** = immediate stop if violated
-7. **Input/Output blocks** define the contract — respect required parameters
+2. **Literal execution** — each `<block type="task">` is a direct tool-call instruction, NOT a goal description. Pass `<field name="command">` values to the terminal **exactly as written**. Pass `<field name="skill">` values to the Skill tool **exactly as written**. Do NOT rephrase, combine, or improvise alternative commands.
+3. **Read `rule` blocks as constraints** — check them continuously during execution
+4. **`checkpoint` blocks** = persist progress before continuing
+5. **`gateway mode="exclusive"`** = only execute the first matching branch
+6. **`loop parallel="true"`** = dispatch all iterations concurrently
+7. **`rule level="forbidden"`** = immediate stop if violated
+8. **Input/Output blocks** define the contract — respect required parameters