speccrew 0.7.51 → 0.7.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.
|
@@ -20,7 +20,7 @@ tools: Read, Write, Glob, Grep, Bash, Agent
|
|
|
20
20
|
> Action-to-tool mapping:
|
|
21
21
|
> - `action="run-skill"` → Invoke via **Skill tool** (pass the `<field name="skill">` value EXACTLY)
|
|
22
22
|
> - `action="run-script"` → Execute via **Terminal tool** (pass the `<field name="command">` value EXACTLY)
|
|
23
|
-
> - `action="dispatch-to-worker"` →
|
|
23
|
+
> - `action="dispatch-to-worker"` → Use **Agent tool** to create a new `speccrew-task-worker` agent, passing skill_path and context
|
|
24
24
|
> - `action="read-file"` → Read via **Read tool**
|
|
25
25
|
> - `action="log"` → Output message directly
|
|
26
26
|
> - `action="confirm"` → Present to user and wait for response
|
|
@@ -93,13 +93,17 @@ This skill MUST execute tasks continuously without unnecessary interruptions.
|
|
|
93
93
|
3. Unrecoverable errors that prevent further progress
|
|
94
94
|
4. Security-sensitive operations (e.g., deleting existing files)
|
|
95
95
|
|
|
96
|
-
### Phase 3
|
|
96
|
+
### Phase 3 Execution Method — Worker Agent Dispatch
|
|
97
97
|
|
|
98
|
-
|
|
99
|
-
|
|
100
|
-
|
|
101
|
-
|
|
102
|
-
|
|
98
|
+
**HOW TO DISPATCH**: When executing Phase 3 block P3-B1 (action="dispatch-to-worker"):
|
|
99
|
+
1. Use the **Agent tool** to create a new `speccrew-task-worker` agent
|
|
100
|
+
2. Pass `skill_path` to the worker: `${workspace_path}/.speccrew/skills/speccrew-sd-framework-evaluate/SKILL.md`
|
|
101
|
+
3. Pass context parameters: workspace_path, iteration_path, feature_spec_paths, api_contract_paths, techs_knowledge_paths, output_path
|
|
102
|
+
4. **Wait** for the worker agent to complete and return results
|
|
103
|
+
5. After worker completes, verify framework-evaluation.md exists at output_path
|
|
104
|
+
6. Then proceed to Phase 3.5 HARD STOP for user confirmation
|
|
105
|
+
|
|
106
|
+
**CRITICAL**: The `Agent tool` creates a NEW agent session — this is completely different from the `Skill tool` which executes inline.
|
|
103
107
|
|
|
104
108
|
### HARD STOP Checkpoints
|
|
105
109
|
|
|
@@ -108,3 +112,21 @@ This workflow has **mandatory HARD STOP** checkpoints at:
|
|
|
108
112
|
- **Phase 6.1**: Joint design confirmation (user MUST approve all designs)
|
|
109
113
|
|
|
110
114
|
DO NOT proceed past these checkpoints without explicit user confirmation.
|
|
115
|
+
|
|
116
|
+
## Must Do
|
|
117
|
+
|
|
118
|
+
- **READ workflow.agentflow.xml FIRST** — Execute blocks in document order
|
|
119
|
+
- **Use Agent tool for dispatch-to-worker blocks** — Agent tool creates a new speccrew-task-worker agent session
|
|
120
|
+
- **Pass skill_path explicitly to worker** — Worker cannot find skills via glob on first run
|
|
121
|
+
- **Wait for worker completion before verifying output** — Do not proceed until worker returns
|
|
122
|
+
- **Update progress via update-progress.js script** — Use run-script commands exactly as defined in XML
|
|
123
|
+
|
|
124
|
+
## Must Not Do
|
|
125
|
+
|
|
126
|
+
- **DO NOT use Skill tool for Phase 3 framework evaluation** — Skill tool executes inline, Agent tool creates a worker
|
|
127
|
+
- **DO NOT read feature spec files yourself** — Workers read them
|
|
128
|
+
- **DO NOT read tech knowledge files yourself** — Workers read them
|
|
129
|
+
- **DO NOT generate framework-evaluation.md yourself** — Only workers generate it
|
|
130
|
+
- **DO NOT create scripts for batch analysis** — Workers handle this via their own skill
|
|
131
|
+
- **DO NOT fallback to inline execution if worker fails** — ABORT instead
|
|
132
|
+
- **DO NOT skip reading workflow.agentflow.xml** — XML is the execution authority
|
|
@@ -168,6 +168,7 @@
|
|
|
168
168
|
<field name="text">FORBIDDEN: Do NOT create scripts or read feature files yourself for framework evaluation</field>
|
|
169
169
|
<field name="text">MANDATORY: Framework evaluation MUST be delegated to worker agent via block P3-B1</field>
|
|
170
170
|
<field name="text">If worker dispatch fails, ABORT — do NOT fallback to inline execution</field>
|
|
171
|
+
<field name="text">TOOL MAPPING: action="dispatch-to-worker" → Use Agent tool (NOT Skill tool) to create speccrew-task-worker agent</field>
|
|
171
172
|
</block>
|
|
172
173
|
|
|
173
174
|
<block type="rule" id="P3-R1" level="mandatory" desc="Worker Dispatch Rule">
|
|
@@ -178,7 +179,7 @@
|
|
|
178
179
|
|
|
179
180
|
<!-- Step 3.1: Dispatch Worker Agent for Framework Evaluation -->
|
|
180
181
|
<block type="task" id="P3-B1" action="dispatch-to-worker" status="pending"
|
|
181
|
-
desc="Dispatch single worker agent for framework evaluation">
|
|
182
|
+
desc="Dispatch single worker agent for framework evaluation. Use /speccrew-task-worker agent, NOT Skill tool">
|
|
182
183
|
<field name="agent">speccrew-task-worker</field>
|
|
183
184
|
<field name="skill">speccrew-sd-framework-evaluate</field>
|
|
184
185
|
<field name="max_concurrent">1</field>
|