speccrew 0.7.68 → 0.7.70
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.
- package/.speccrew/agents/speccrew-system-designer.md +5 -1
- package/.speccrew/agents/speccrew-task-worker.md +5 -1
- package/.speccrew/skills/speccrew-system-designer-orchestration/SKILL.md +34 -0
- package/.speccrew/skills/speccrew-system-designer-orchestration/SKILL.xml +5 -0
- package/package.json +1 -1
|
@@ -17,7 +17,11 @@ Your core task is: based on the Feature Spec (WHAT to build), design HOW to buil
|
|
|
17
17
|
|
|
18
18
|
**Agent MUST follow this protocol when starting any skill execution:**
|
|
19
19
|
|
|
20
|
-
1. **Load XML First**: Before
|
|
20
|
+
1. **Load XML First**: Before ANY other action, locate and read the skill's SKILL.xml:
|
|
21
|
+
- Skill directory: find the skill folder under the IDE skills directory (e.g., `.qoder/skills/{skill-name}/` or `.speccrew/skills/{skill-name}/`)
|
|
22
|
+
- Read `SKILL.xml` from that directory immediately
|
|
23
|
+
- Do NOT explore workspace structure, check files, or run commands before loading XML
|
|
24
|
+
- If SKILL.xml read fails, report error and ABORT — do NOT attempt to proceed without it
|
|
21
25
|
2. **Announce Workflow**: Log the workflow phases/steps overview from XML structure
|
|
22
26
|
3. **Execute Blocks Sequentially**: Follow SKILL.xml block order strictly — do NOT improvise or skip blocks
|
|
23
27
|
4. **Report Progress**: Before each Phase/Step, announce: "📍 Phase X: {name}" or "⏳ Step X.X: {description}"
|
|
@@ -8,7 +8,11 @@ tools: Read, Grep, Glob, Write, Bash, Edit, WebFetch, WebSearch
|
|
|
8
8
|
|
|
9
9
|
**Worker MUST follow this protocol for EVERY task execution:**
|
|
10
10
|
|
|
11
|
-
1. **Load Skill XML First**:
|
|
11
|
+
1. **Load Skill XML First**: IMMEDIATELY read the assigned skill's SKILL.xml:
|
|
12
|
+
- If `skill_path` is provided in dispatch context, read `${skill_path}/SKILL.xml`
|
|
13
|
+
- If `skill_name` is provided, find skill folder under IDE skills directory and read its SKILL.xml
|
|
14
|
+
- This MUST be the FIRST action — before reading ANY other file, exploring directories, or running commands
|
|
15
|
+
- If SKILL.xml read fails, report error with the attempted path and ABORT
|
|
12
16
|
2. **Announce Block Execution**: Before each block, output: `[Block {ID}] {description}`
|
|
13
17
|
3. **Execute Blocks Sequentially**: Follow SKILL.xml block order strictly — do NOT improvise, skip, or reorder blocks
|
|
14
18
|
4. **Honor Dispatch Context**: Accept all context parameters (task_id, feature_id, platform, skip_confirmation, etc.) as authoritative — do NOT question or validate them
|
|
@@ -10,6 +10,40 @@ tools: Read, Write, Glob, Grep, Bash, Agent
|
|
|
10
10
|
- Feature Spec and API Contract have been confirmed (02_feature_design stage = confirmed)
|
|
11
11
|
- User requests system design execution for confirmed features
|
|
12
12
|
|
|
13
|
+
## EXECUTION PROTOCOL
|
|
14
|
+
|
|
15
|
+
### Action-to-Tool Mapping
|
|
16
|
+
|
|
17
|
+
| XML Block Action | IDE Tool | How to Execute |
|
|
18
|
+
|---|---|---|
|
|
19
|
+
| `action="run-script"` | **Terminal tool** | Execute command in terminal |
|
|
20
|
+
| `action="dispatch-to-worker"` | **Agent tool** | Create new `speccrew-task-worker` agent session (NOT Skill tool) |
|
|
21
|
+
| `action="read-file"` | **Read tool** | Read file at specified path |
|
|
22
|
+
| `action="log"` | **Output** | Log message directly to conversation |
|
|
23
|
+
| `action="confirm"` | **Output + Wait** | Present message and wait for user response |
|
|
24
|
+
|
|
25
|
+
### Worker Dispatch Protocol
|
|
26
|
+
|
|
27
|
+
When executing any block with `action="dispatch-to-worker"`:
|
|
28
|
+
|
|
29
|
+
1. **Use Agent tool** to create a new `speccrew-task-worker` agent
|
|
30
|
+
2. Pass `skill_path` from the XML `<field name="skill_path">` to worker
|
|
31
|
+
3. Pass all context parameters from XML `<field name="context">` block
|
|
32
|
+
4. **Wait** for worker agent to complete before proceeding to next block
|
|
33
|
+
5. Verify worker's output file exists at expected path
|
|
34
|
+
|
|
35
|
+
**CRITICAL DISTINCTION**:
|
|
36
|
+
- **Agent tool** = creates a NEW autonomous worker session (for dispatch-to-worker)
|
|
37
|
+
- **Skill tool** = executes skill inline in current session (for run-skill)
|
|
38
|
+
- Using the WRONG tool will cause dispatch failure
|
|
39
|
+
|
|
40
|
+
### Phase 5 Batch Dispatch
|
|
41
|
+
|
|
42
|
+
- Dispatch ONE worker per Feature×Platform combination via Agent tool
|
|
43
|
+
- Max concurrent workers per batch: defined in XML
|
|
44
|
+
- Pass `skip_confirmation: true` and `skip_index_generation: true` in batch context
|
|
45
|
+
- Wait for all workers in current batch to complete before dispatching next batch
|
|
46
|
+
|
|
13
47
|
## AgentFlow Definition
|
|
14
48
|
|
|
15
49
|
<!-- @agentflow: SKILL.xml -->
|
|
@@ -8,6 +8,11 @@
|
|
|
8
8
|
<field name="current_iteration" required="false" type="string" desc="Current active iteration identifier"/>
|
|
9
9
|
</block>
|
|
10
10
|
|
|
11
|
+
<!-- Step 0: Load this workflow definition -->
|
|
12
|
+
<block type="event" id="LOAD-LOG" action="log" desc="Loading workflow XML">
|
|
13
|
+
<field name="message">[Block LOAD] 正在加载 SKILL.xml 工作流定义...</field>
|
|
14
|
+
</block>
|
|
15
|
+
|
|
11
16
|
<!-- ========== Workflow Loading Announcement ========== -->
|
|
12
17
|
<sequence name="工作流加载播报">
|
|
13
18
|
<block type="event" id="LOAD-ANNOUNCE" action="log" desc="Workflow loading announcement">
|