speccrew 0.6.49 → 0.6.51

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/.speccrew/agents/speccrew-team-leader-xml.md +4 -1
  2. package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md +2 -0
  3. package/.speccrew/skills/speccrew-knowledge-techs-dispatch-xml/SKILL.md +2 -0
  4. package/package.json +1 -1
  5. package/workspace-template/docs/rules/xml-workflow-spec.md +7 -6
package/.speccrew/agents/speccrew-team-leader-xml.md CHANGED
@@ -75,9 +75,12 @@ You understand the complete AI engineering closed loop: **speccrew-pm → speccr
75
75
 
76
76
  # Workflow (XML Block Definition)
77
77
 
78
- > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `docs/rules/xml-workflow-spec.md`
78
+ > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
79
+ >
80
+ > 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.
79
81
 
80
82
  ```xml
83
+ <?xml version="1.0" encoding="UTF-8"?>
81
84
  <workflow id="team-leader-main" status="pending">
82
85
 
83
86
  <block type="input" id="I1" desc="User request input">
package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md CHANGED
@@ -99,6 +99,8 @@ Stage 4: System Summary
99
99
  ## XML Workflow Definition
100
100
 
101
101
  > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
102
+ >
103
+ > 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.
102
104
 
103
105
  ```xml
104
106
  <?xml version="1.0" encoding="UTF-8"?>
package/.speccrew/skills/speccrew-knowledge-techs-dispatch-xml/SKILL.md CHANGED
@@ -119,6 +119,8 @@ Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized pl
119
119
  ## XML Workflow Definition
120
120
 
121
121
  > **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
122
+ >
123
+ > 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.
122
124
 
123
125
  ```xml
124
126
  <?xml version="1.0" encoding="UTF-8"?>
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "speccrew",
3
- "version": "0.6.49",
3
+ "version": "0.6.51",
4
4
  "description": "Spec-Driven Development toolkit for AI-powered IDEs",
5
5
  "author": "charlesmu99",
6
6
  "repository": {
package/workspace-template/docs/rules/xml-workflow-spec.md CHANGED
@@ -393,9 +393,10 @@ When executing `<block type="task">` blocks, the `action` attribute determines w
393
393
  ## Execution Rules
394
394
 
395
395
  1. **NEVER skip a block** — execute every block in document order
396
- 2. **Read `rule` blocks as constraints** — check them continuously during execution
397
- 3. **`checkpoint` blocks** = persist progress before continuing
398
- 4. **`gateway mode="exclusive"`** = only execute the first matching branch
399
- 5. **`loop parallel="true"`** = dispatch all iterations concurrently
400
- 6. **`rule level="forbidden"`** = immediate stop if violated
401
- 7. **Input/Output blocks** define the contract — respect required parameters
396
+ 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.
397
+ 3. **Read `rule` blocks as constraints** — check them continuously during execution
398
+ 4. **`checkpoint` blocks** = persist progress before continuing
399
+ 5. **`gateway mode="exclusive"`** = only execute the first matching branch
400
+ 6. **`loop parallel="true"`** = dispatch all iterations concurrently
401
+ 7. **`rule level="forbidden"`** = immediate stop if violated
402
+ 8. **Input/Output blocks** define the contract — respect required parameters