speccrew 0.6.40 → 0.6.41

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 (4) hide show
  1. package/.speccrew/agents/speccrew-team-leader-xml.md +9 -37
  2. package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md +21 -7
  3. package/.speccrew/skills/speccrew-knowledge-techs-dispatch-xml/SKILL.md +21 -7
  4. package/package.json +1 -1
package/.speccrew/agents/speccrew-team-leader-xml.md CHANGED
@@ -190,16 +190,9 @@ rule : Constraint declaration (level: forbidden | mandatory | note)
190
190
  <block type="rule" id="P05-R-TECHS" level="mandatory" desc="Parallel worker dispatch for techs">
191
191
  <field name="text">When techs-dispatch Stage 2 prepares task plans for multiple platforms, dispatch ALL platform workers IN PARALLEL — DO NOT execute sequentially</field>
192
192
  </block>
193
- <block type="task" id="P05-B5" action="dispatch-to-worker" desc="Dispatch techs-dispatch via Task tool → speccrew-task-worker">
194
- <field name="worker">speccrew-task-worker</field>
193
+ <block type="task" id="P05-B5" action="run-skill" desc="Leader directly invokes techs-dispatch as orchestration playbook">
195
194
  <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
196
- <field name="instructions">
197
- CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
198
-
199
- Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-techs-dispatch-xml.
200
- The Worker Agent will load and execute the dispatch workflow autonomously.
201
- DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
202
- </field>
195
+ <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
203
196
  </block>
204
197
  </branch>
205
198
  <branch test="${bizs_kb.exists} == false" name="Bizs Not Initialized">
@@ -207,16 +200,9 @@ DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
207
200
  <block type="rule" id="P05-R-BIZS" level="mandatory" desc="Parallel worker dispatch for bizs">
208
201
  <field name="text">When bizs-dispatch prepares worker task plans, dispatch ALL workers IN PARALLEL per stage — DO NOT execute sequentially</field>
209
202
  </block>
210
- <block type="task" id="P05-B6" action="dispatch-to-worker" desc="Dispatch bizs-dispatch via Task tool → speccrew-task-worker">
211
- <field name="worker">speccrew-task-worker</field>
203
+ <block type="task" id="P05-B6" action="run-skill" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
212
204
  <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
213
- <field name="instructions">
214
- CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
215
-
216
- Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-bizs-dispatch-xml.
217
- The Worker Agent will load and execute the dispatch workflow autonomously.
218
- DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
219
- </field>
205
+ <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
220
206
  </block>
221
207
  </branch>
222
208
  <branch default="true" name="Knowledge Base Ready">
@@ -237,7 +223,7 @@ DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
237
223
  <field name="text">DO NOT trigger business process Skills (PRD, Solution, Design, Dev) — these are loaded by corresponding role Agents</field>
238
224
  <field name="text">DO NOT handle business development requests (feature requirements, code modifications, bug fixes) — prompt user to talk directly to Qoder</field>
239
225
  <field name="text">DO NOT delete or modify WORKFLOW-PROGRESS.json (read-only)</field>
240
- <field name="text">DO NOT call the Skill tool directly for speccrew-knowledge-* skills (speccrew-knowledge-bizs-dispatch-xml, speccrew-knowledge-techs-dispatch-xml) — MUST use Task tool to create speccrew-task-worker Agent for indirect execution</field>
226
+ <field name="text">dispatch skills (bizs-dispatch-xml, techs-dispatch-xml) MUST be called directly by Leader via Skill tool as orchestration playbooks. Downstream worker skills (identify-entries, init-features, ui-analyze, etc.) MUST be dispatched via Task tool → speccrew-task-worker.</field>
241
227
  </block>
242
228
 
243
229
  <block type="gateway" id="P1-G1" mode="exclusive" desc="Intent Recognition Routing">
@@ -257,16 +243,9 @@ DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
257
243
  <field name="text">When bizs-dispatch prepares worker task plans for multiple features or platforms, dispatch ALL workers IN PARALLEL — DO NOT execute features or platforms sequentially one by one</field>
258
244
  <field name="text">Each Worker (analysis, graph, summarize) runs independently — dispatch all of them at once per stage, then monitor completion markers</field>
259
245
  </block>
260
- <block type="task" id="P1-B3" action="dispatch-to-worker" status="pending" desc="Dispatch bizs-dispatch via Task tool → speccrew-task-worker">
261
- <field name="worker">speccrew-task-worker</field>
246
+ <block type="task" id="P1-B3" action="run-skill" status="pending" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
262
247
  <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
263
- <field name="instructions">
264
- CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
265
-
266
- Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-bizs-dispatch-xml.
267
- The Worker Agent will load and execute the dispatch workflow autonomously.
268
- DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
269
- </field>
248
+ <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
270
249
  </block>
271
250
  </branch>
272
251
  <branch test="${intent} == 'knowledge_techs'" name="Techs Knowledge Base">
@@ -274,16 +253,9 @@ DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
274
253
  <field name="text">When techs-dispatch Stage 2 prepares task plans for multiple platforms, dispatch ALL platform workers IN PARALLEL using concurrent task dispatch — DO NOT execute platforms sequentially one by one</field>
275
254
  <field name="text">Each platform worker (techs-generate-conventions, techs-generate-ui-style) runs independently — dispatch all of them at once, then monitor completion markers</field>
276
255
  </block>
277
- <block type="task" id="P1-B4" action="dispatch-to-worker" status="pending" desc="Dispatch techs-dispatch via Task tool → speccrew-task-worker">
278
- <field name="worker">speccrew-task-worker</field>
256
+ <block type="task" id="P1-B4" action="run-skill" status="pending" desc="Leader directly invokes techs-dispatch as orchestration playbook">
279
257
  <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
280
- <field name="instructions">
281
- CRITICAL: This skill MUST be invoked via Task tool creating a Worker Agent (speccrew-task-worker), NOT via direct Skill tool call.
282
-
283
- Use the Task tool to create a Worker Agent with the skill speccrew-knowledge-techs-dispatch-xml.
284
- The Worker Agent will load and execute the dispatch workflow autonomously.
285
- DO NOT call the Skill tool directly for speccrew-knowledge-* skills.
286
- </field>
258
+ <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
287
259
  </block>
288
260
  </branch>
289
261
 
package/.speccrew/skills/speccrew-knowledge-bizs-dispatch-xml/SKILL.md CHANGED
@@ -10,24 +10,29 @@ Orchestrate **bizs knowledge base generation** with a 5-stage pipeline using **X
10
10
 
11
11
  ## Invocation Method
12
12
 
13
- **CRITICAL**: This skill MUST be invoked via Task tool → speccrew-task-worker, NOT via direct Skill tool call.
13
+ **CRITICAL**: This skill is an **orchestration playbook** — it MUST be loaded directly by Team Leader via Skill tool (NOT via Worker Agent).
14
14
 
15
15
  ```
16
- Correct: Use Task tool to create speccrew-task-worker with this skill
17
- Incorrect: Use Skill tool to call this skill directly
16
+ Correct: Leader uses Skill tool to load this playbook directly
17
+ Incorrect: Dispatch this skill to speccrew-task-worker
18
18
  ```
19
19
 
20
- **Why?** This skill requires run_in_terminal capability for script execution, which Worker Agents possess but direct Skill invocations may not support correctly. The Task tool creates a dedicated Worker Agent (speccrew-task-worker) that loads and executes this workflow autonomously.
20
+ **Why?** This skill defines the orchestration workflow and prepares task plans for downstream workers. The Team Leader reads this playbook and dispatches individual worker tasks via Task tool → speccrew-task-worker for each stage.
21
21
 
22
22
  **Correct Invocation Pattern**:
23
23
  ```xml
24
- <block type="task" action="dispatch-to-worker" desc="Dispatch bizs-dispatch via Task tool">
25
- <field name="worker">speccrew-task-worker</field>
24
+ <block type="task" action="run-skill" desc="Leader directly invokes bizs-dispatch as orchestration playbook">
26
25
  <field name="skill">speccrew-knowledge-bizs-dispatch-xml</field>
27
- <field name="instructions">Execute the bizs knowledge base generation pipeline.</field>
26
+ <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
28
27
  </block>
29
28
  ```
30
29
 
30
+ **Worker Dispatch Rule**:
31
+ - Dispatch skills (bizs-dispatch-xml, techs-dispatch-xml): Leader calls directly via Skill tool
32
+ - Downstream worker skills (identify-entries, init-features, ui-analyze, module-summarize, etc.): Leader dispatches via Task tool → speccrew-task-worker
33
+
34
+ **FORBIDDEN**: Worker Agents MUST NOT execute this dispatch skill. If a Worker Agent loads this skill, it must report error and abort.
35
+
31
36
  ## Quick Reference — Execution Flow
32
37
 
33
38
  ```
@@ -114,6 +119,15 @@ Stage 4: System Summary
114
119
  <field name="completed_dir" required="true" type="string" desc="Marker file output directory for Worker results (absolute path required)"/>
115
120
  </block>
116
121
 
122
+ <!-- ============================================================
123
+ Global Invocation Rules
124
+ ============================================================ -->
125
+ <block type="rule" id="GLOBAL-R-INVOCATION" level="forbidden" desc="Invocation constraints — NEVER violate">
126
+ <field name="text">This skill is an ORCHESTRATION PLAYBOOK — it MUST be loaded directly by Team Leader via Skill tool</field>
127
+ <field name="text">Worker Agents MUST NOT execute this dispatch skill — if loaded by a Worker, report error and abort</field>
128
+ <field name="text">Downstream worker skills (identify-entries, init-features, ui-analyze, module-summarize, etc.) MUST be dispatched via Task tool → speccrew-task-worker</field>
129
+ </block>
130
+
117
131
  <!-- ============================================================
118
132
  Global Continuous Execution Rules
119
133
  ============================================================ -->
package/.speccrew/skills/speccrew-knowledge-techs-dispatch-xml/SKILL.md CHANGED
@@ -10,24 +10,29 @@ Orchestrate **techs knowledge base generation** with a 3-stage pipeline using **
10
10
 
11
11
  ## Invocation Method
12
12
 
13
- **CRITICAL**: This skill MUST be invoked via Task tool → speccrew-task-worker, NOT via direct Skill tool call.
13
+ **CRITICAL**: This skill is an **orchestration playbook** — it MUST be loaded directly by Team Leader via Skill tool (NOT via Worker Agent).
14
14
 
15
15
  ```
16
- Correct: Use Task tool to create speccrew-task-worker with this skill
17
- Incorrect: Use Skill tool to call this skill directly
16
+ Correct: Leader uses Skill tool to load this playbook directly
17
+ Incorrect: Dispatch this skill to speccrew-task-worker
18
18
  ```
19
19
 
20
- **Why?** This skill requires run_in_terminal capability for script execution, which Worker Agents possess but direct Skill invocations may not support correctly. The Task tool creates a dedicated Worker Agent (speccrew-task-worker) that loads and executes this workflow autonomously.
20
+ **Why?** This skill defines the orchestration workflow and prepares task plans for downstream workers. The Team Leader reads this playbook and dispatches individual worker tasks via Task tool → speccrew-task-worker for each stage.
21
21
 
22
22
  **Correct Invocation Pattern**:
23
23
  ```xml
24
- <block type="task" action="dispatch-to-worker" desc="Dispatch techs-dispatch via Task tool">
25
- <field name="worker">speccrew-task-worker</field>
24
+ <block type="task" action="run-skill" desc="Leader directly invokes techs-dispatch as orchestration playbook">
26
25
  <field name="skill">speccrew-knowledge-techs-dispatch-xml</field>
27
- <field name="instructions">Execute the techs knowledge base generation pipeline.</field>
26
+ <field name="note">Leader directly calls this dispatch skill as an orchestration playbook. The dispatch skill defines the workflow; Leader dispatches downstream workers via Task tool → speccrew-task-worker for each stage.</field>
28
27
  </block>
29
28
  ```
30
29
 
30
+ **Worker Dispatch Rule**:
31
+ - Dispatch skills (bizs-dispatch-xml, techs-dispatch-xml): Leader calls directly via Skill tool
32
+ - Downstream worker skills (techs-init, techs-generate-conventions, techs-generate-ui-style, etc.): Leader dispatches via Task tool → speccrew-task-worker
33
+
34
+ **FORBIDDEN**: Worker Agents MUST NOT execute this dispatch skill. If a Worker Agent loads this skill, it must report error and abort.
35
+
31
36
  ## Quick Reference — Execution Flow
32
37
 
33
38
  ```
@@ -127,6 +132,15 @@ Read `speccrew-workspace/docs/configs/platform-mapping.json` for standardized pl
127
132
  <field name="ide_skills_dir" required="true" type="string" desc="Absolute path to IDE skills directory (e.g., .qoder/skills, .cursor/skills)"/>
128
133
  </block>
129
134
 
135
+ <!-- ============================================================
136
+ Global Invocation Rules
137
+ ============================================================ -->
138
+ <block type="rule" id="GLOBAL-R-INVOCATION" level="forbidden" desc="Invocation constraints — NEVER violate">
139
+ <field name="text">This skill is an ORCHESTRATION PLAYBOOK — it MUST be loaded directly by Team Leader via Skill tool</field>
140
+ <field name="text">Worker Agents MUST NOT execute this dispatch skill — if loaded by a Worker, report error and abort</field>
141
+ <field name="text">Downstream worker skills (techs-init, techs-generate-conventions, techs-generate-ui-style, etc.) MUST be dispatched via Task tool → speccrew-task-worker</field>
142
+ </block>
143
+
130
144
  <!-- ============================================================
131
145
  Global Continuous Execution Rules
132
146
  ============================================================ -->
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "speccrew",
3
- "version": "0.6.40",
3
+ "version": "0.6.41",
4
4
  "description": "Spec-Driven Development toolkit for AI-powered IDEs",
5
5
  "author": "charlesmu99",
6
6
  "repository": {