speccrew 0.6.52 → 0.6.53
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.
|
@@ -77,7 +77,15 @@ You understand the complete AI engineering closed loop: **speccrew-pm → speccr
|
|
|
77
77
|
|
|
78
78
|
> **REQUIRED**: Before executing this workflow, read the XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md`
|
|
79
79
|
>
|
|
80
|
-
> After reading the specification, parse the XML workflow below and **strictly execute each `<block>` in document order**.
|
|
80
|
+
> 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:
|
|
81
|
+
>
|
|
82
|
+
> ```
|
|
83
|
+
> 📋 Block [ID] (action=[action]) — [desc]
|
|
84
|
+
> 🔧 Tool: [which IDE tool to call]
|
|
85
|
+
> ✅ Result: [output or status]
|
|
86
|
+
> ```
|
|
87
|
+
>
|
|
88
|
+
> 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**. For `action="dispatch-to-worker"`, create a Task for the Worker Agent — do NOT execute the skill yourself. Do NOT interpret the workflow as a goal description or improvise your own approach.
|
|
81
89
|
|
|
82
90
|
```xml
|
|
83
91
|
<?xml version="1.0" encoding="UTF-8"?>
|
|
@@ -8,15 +8,28 @@ tools: Read, Write, Task, Bash
|
|
|
8
8
|
>
|
|
9
9
|
> **Step 1**: Load XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md` — this defines all block types and action-to-tool mappings
|
|
10
10
|
>
|
|
11
|
-
> **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order
|
|
12
|
-
>
|
|
13
|
-
>
|
|
14
|
-
>
|
|
11
|
+
> **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:
|
|
12
|
+
>
|
|
13
|
+
> ```
|
|
14
|
+
> 📋 Block [ID] (action=[action]) — [desc]
|
|
15
|
+
> 🔧 Tool: [which IDE tool to call]
|
|
16
|
+
> ✅ Result: [output or status]
|
|
17
|
+
> ```
|
|
18
|
+
>
|
|
19
|
+
> Action-to-tool mapping:
|
|
20
|
+
> - `action="run-script"` → Execute via **Terminal tool** (pass the `<field name="command">` value EXACTLY)
|
|
21
|
+
> - `action="run-skill"` → Invoke via **Skill tool** (pass the `<field name="skill">` value EXACTLY)
|
|
22
|
+
> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker` (Worker loads and executes the skill, NOT you)
|
|
15
23
|
> - `action="confirm"` (event) → Present to user and wait for response
|
|
16
24
|
>
|
|
17
25
|
> **Step 3**: Execute ALL stages sequentially without pausing (only stop at explicit `<event action="confirm">` blocks)
|
|
18
26
|
>
|
|
19
|
-
> **FORBIDDEN**:
|
|
27
|
+
> **FORBIDDEN**:
|
|
28
|
+
> - Do NOT skip the block announcement format above — every block must be announced before execution
|
|
29
|
+
> - Do NOT run terminal commands as substitute for Skill tool calls
|
|
30
|
+
> - Do NOT do Worker's job yourself — when `action="dispatch-to-worker"`, create a Task and let Worker handle it
|
|
31
|
+
> - Do NOT skip blocks or improvise your own commands
|
|
32
|
+
> - Do NOT read a skill's SKILL.md file yourself — use the Skill tool which resolves paths automatically
|
|
20
33
|
|
|
21
34
|
# Bizs Knowledge Dispatch (XML Block Version)
|
|
22
35
|
|
|
@@ -8,15 +8,28 @@ tools: Read, Write, Task, Bash
|
|
|
8
8
|
>
|
|
9
9
|
> **Step 1**: Load XML workflow specification: `speccrew-workspace/docs/rules/xml-workflow-spec.md` — this defines all block types and action-to-tool mappings
|
|
10
10
|
>
|
|
11
|
-
> **Step 2**: Execute this SKILL.md's XML workflow **block by block in document order
|
|
12
|
-
>
|
|
13
|
-
>
|
|
14
|
-
>
|
|
11
|
+
> **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:
|
|
12
|
+
>
|
|
13
|
+
> ```
|
|
14
|
+
> 📋 Block [ID] (action=[action]) — [desc]
|
|
15
|
+
> 🔧 Tool: [which IDE tool to call]
|
|
16
|
+
> ✅ Result: [output or status]
|
|
17
|
+
> ```
|
|
18
|
+
>
|
|
19
|
+
> Action-to-tool mapping:
|
|
20
|
+
> - `action="run-script"` → Execute via **Terminal tool** (pass the `<field name="command">` value EXACTLY)
|
|
21
|
+
> - `action="run-skill"` → Invoke via **Skill tool** (pass the `<field name="skill">` value EXACTLY)
|
|
22
|
+
> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker` (Worker loads and executes the skill, NOT you)
|
|
15
23
|
> - `action="confirm"` (event) → Present to user and wait for response
|
|
16
24
|
>
|
|
17
25
|
> **Step 3**: Execute ALL stages sequentially without pausing (only stop at explicit `<event action="confirm">` blocks)
|
|
18
26
|
>
|
|
19
|
-
> **FORBIDDEN**:
|
|
27
|
+
> **FORBIDDEN**:
|
|
28
|
+
> - Do NOT skip the block announcement format above — every block must be announced before execution
|
|
29
|
+
> - Do NOT run terminal commands as substitute for Skill tool calls
|
|
30
|
+
> - Do NOT do Worker's job yourself — when `action="dispatch-to-worker"`, create a Task and let Worker handle it
|
|
31
|
+
> - Do NOT skip blocks or improvise your own commands
|
|
32
|
+
> - Do NOT read a skill's SKILL.md file yourself — use the Skill tool which resolves paths automatically
|
|
20
33
|
|
|
21
34
|
# Techs Knowledge Dispatch (XML Block Version)
|
|
22
35
|
|