speccrew 0.7.3 → 0.7.5
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-feature-designer.md +6 -0
- package/.speccrew/agents/speccrew-product-manager.md +6 -0
- package/.speccrew/agents/speccrew-system-deployer.md +6 -0
- package/.speccrew/agents/speccrew-system-designer.md +6 -0
- package/.speccrew/agents/speccrew-system-developer.md +6 -0
- package/.speccrew/agents/speccrew-task-worker.md +5 -0
- package/.speccrew/agents/speccrew-team-leader.md +7 -1
- package/.speccrew/agents/speccrew-test-manager.md +6 -0
- package/.speccrew/skills/speccrew-feature-designer-orchestration/SKILL.md +117 -0
- package/.speccrew/skills/speccrew-feature-designer-orchestration/workflow.agentflow.xml +463 -0
- package/.speccrew/skills/speccrew-product-manager-orchestration/SKILL.md +111 -0
- package/.speccrew/skills/speccrew-product-manager-orchestration/workflow.agentflow.xml +534 -0
- package/.speccrew/skills/speccrew-system-deployer-orchestration/SKILL.md +91 -0
- package/.speccrew/skills/speccrew-system-deployer-orchestration/workflow.agentflow.xml +309 -0
- package/.speccrew/skills/speccrew-system-designer-orchestration/SKILL.md +102 -0
- package/.speccrew/skills/speccrew-system-designer-orchestration/workflow.agentflow.xml +375 -0
- package/.speccrew/skills/speccrew-system-developer-orchestration/SKILL.md +110 -0
- package/.speccrew/skills/speccrew-system-developer-orchestration/workflow.agentflow.xml +422 -0
- package/.speccrew/skills/speccrew-task-worker-execution/SKILL.md +106 -0
- package/.speccrew/skills/speccrew-task-worker-execution/workflow.agentflow.xml +177 -0
- package/.speccrew/skills/speccrew-team-leader-routing/SKILL.md +91 -0
- package/.speccrew/{agents → skills/speccrew-team-leader-routing}/workflow.agentflow.xml +1 -1
- package/.speccrew/skills/speccrew-test-manager-orchestration/SKILL.md +106 -0
- package/.speccrew/skills/speccrew-test-manager-orchestration/workflow.agentflow.xml +442 -0
- package/package.json +1 -1
|
@@ -145,6 +145,12 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
|
|
|
145
145
|
|
|
146
146
|
# Workflow
|
|
147
147
|
|
|
148
|
+
## AgentFlow Definition
|
|
149
|
+
|
|
150
|
+
<!-- @skill: speccrew-feature-designer-orchestration -->
|
|
151
|
+
|
|
152
|
+
---
|
|
153
|
+
|
|
148
154
|
## Phase 0: Workflow Progress Management
|
|
149
155
|
|
|
150
156
|
> **Path Variables** (provided by caller as absolute paths):
|
|
@@ -184,6 +184,12 @@ If WORKFLOW-PROGRESS.json does not exist (legacy iterations or new workspace):
|
|
|
184
184
|
|
|
185
185
|
# Workflow
|
|
186
186
|
|
|
187
|
+
## AgentFlow Definition
|
|
188
|
+
|
|
189
|
+
<!-- @skill: speccrew-product-manager-orchestration -->
|
|
190
|
+
|
|
191
|
+
---
|
|
192
|
+
|
|
187
193
|
## Phase 0.5: IDE Detection
|
|
188
194
|
|
|
189
195
|
Detect current IDE environment and determine skill loading strategy:
|
|
@@ -614,3 +614,9 @@ You can proceed with System Test Agent (speccrew-test-manager).
|
|
|
614
614
|
- Proceed to next skill if current skill fails
|
|
615
615
|
- Proceed to testing phase without user confirmation
|
|
616
616
|
- Hardcode any commands — always read from techs knowledge
|
|
617
|
+
|
|
618
|
+
---
|
|
619
|
+
|
|
620
|
+
## AgentFlow Definition
|
|
621
|
+
|
|
622
|
+
<!-- @skill: speccrew-system-deployer-orchestration -->
|
|
@@ -1022,3 +1022,9 @@ After user confirms:
|
|
|
1022
1022
|
- DO NOT proceed to the next batch or Phase 6 if any Phase 5 batch worker failure rate > 50% — follow the Batch Failure recovery flow in Phase 5.6
|
|
1023
1023
|
- DO NOT skip backward compatibility checks for old format Feature Specs
|
|
1024
1024
|
- DO NOT automatically transition to or invoke the next stage agent — user starts next stage in a new conversation
|
|
1025
|
+
|
|
1026
|
+
---
|
|
1027
|
+
|
|
1028
|
+
## AgentFlow Definition
|
|
1029
|
+
|
|
1030
|
+
<!-- @skill: speccrew-system-designer-orchestration -->
|
|
@@ -1112,3 +1112,9 @@ Delivery Report: {path}/delivery-report.md
|
|
|
1112
1112
|
- Ignore cross-platform integration issues
|
|
1113
1113
|
- Proceed to test phase with unresolved blockers
|
|
1114
1114
|
- Write application code directly (System Developer is a **pure orchestrator** — it reads design documents, creates task lists, dispatches workers, tracks progress, and coordinates reviews. It NEVER writes application code directly.)
|
|
1115
|
+
|
|
1116
|
+
---
|
|
1117
|
+
|
|
1118
|
+
## AgentFlow Definition
|
|
1119
|
+
|
|
1120
|
+
<!-- @skill: speccrew-system-developer-orchestration -->
|
|
@@ -208,3 +208,8 @@ When the task fails or is blocked, output:
|
|
|
208
208
|
- **DO NOT** use Bash/terminal tools to create .py, .bat, .sh, .ps1, or any executable files
|
|
209
209
|
- If the assigned Skill file does not exist or task execution fails, STOP immediately and report the exact error — do not improvise alternative solutions
|
|
210
210
|
|
|
211
|
+
---
|
|
212
|
+
|
|
213
|
+
## AgentFlow Definition
|
|
214
|
+
|
|
215
|
+
<!-- @skill: speccrew-task-worker-execution -->
|
|
@@ -50,6 +50,12 @@ You understand the complete AI engineering closed loop: **speccrew-pm → speccr
|
|
|
50
50
|
|
|
51
51
|
# Skill Inventory
|
|
52
52
|
|
|
53
|
+
## Routing
|
|
54
|
+
|
|
55
|
+
| Skill | Trigger Scenario | Function |
|
|
56
|
+
|-------|------------------|----------|
|
|
57
|
+
| `speccrew-team-leader-routing` | All user inputs | Intent recognition and routing to corresponding Skill/Agent |
|
|
58
|
+
|
|
53
59
|
## Infrastructure (Project-level)
|
|
54
60
|
|
|
55
61
|
| Skill | Trigger Scenario | Function |
|
|
@@ -89,7 +95,7 @@ You understand the complete AI engineering closed loop: **speccrew-pm → speccr
|
|
|
89
95
|
|
|
90
96
|
## AgentFlow Definition
|
|
91
97
|
|
|
92
|
-
<!-- @
|
|
98
|
+
<!-- @skill: speccrew-team-leader-routing -->
|
|
93
99
|
|
|
94
100
|
---
|
|
95
101
|
|
|
@@ -917,3 +917,9 @@ node {update_progress_script} update-workflow --file {workspace_path}/WORKFLOW-P
|
|
|
917
917
|
- Assume business rules; unclear requirements must be traced to Feature Spec or PRD
|
|
918
918
|
- Modify development phase source code
|
|
919
919
|
- Proceed to delivery phase with unresolved critical or high-severity bugs
|
|
920
|
+
|
|
921
|
+
---
|
|
922
|
+
|
|
923
|
+
## AgentFlow Definition
|
|
924
|
+
|
|
925
|
+
<!-- @skill: speccrew-test-manager-orchestration -->
|
|
@@ -0,0 +1,117 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: speccrew-feature-designer-orchestration
|
|
3
|
+
version: 1.0.0
|
|
4
|
+
description: Feature Designer 的核心编排技能,负责加载功能清单、协调功能分析、功能规格设计与 API 契约生成。处理单个功能(直接调用)和多个功能(Worker 分发)两种工作流路径。
|
|
5
|
+
tools: Read, Write, Glob, Grep, Bash, Agent
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
> **⚠️ MANDATORY EXECUTION PROTOCOL — READ BEFORE EXECUTING ANY BLOCK**
|
|
9
|
+
>
|
|
10
|
+
> **Step 1**: Load XML workflow specification: `speccrew-workspace/docs/rules/agentflow-spec.md` — this defines all block types and action-to-tool mappings
|
|
11
|
+
>
|
|
12
|
+
> **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:
|
|
13
|
+
>
|
|
14
|
+
> ```
|
|
15
|
+
> 📋 Block [ID] (action=[action]) — [desc]
|
|
16
|
+
> 🔧 Tool: [which IDE tool to call]
|
|
17
|
+
> ✅ Result: [output or status]
|
|
18
|
+
> ```
|
|
19
|
+
>
|
|
20
|
+
> Action-to-tool mapping:
|
|
21
|
+
> - `action="run-skill"` → Invoke via **Skill tool** (pass the `<field name="skill">` value EXACTLY)
|
|
22
|
+
> - `action="run-script"` → Execute via **Terminal tool** (pass the `<field name="command">` value EXACTLY)
|
|
23
|
+
> - `action="dispatch-to-worker"` → Create **Task** via **Task tool** for `speccrew-task-worker`
|
|
24
|
+
> - `action="read-file"` → Read via **Read tool**
|
|
25
|
+
> - `action="log"` → Output message directly
|
|
26
|
+
> - `action="confirm"` → Present to user and wait for response
|
|
27
|
+
>
|
|
28
|
+
> **Step 3**: Execute ALL blocks sequentially without pausing (only stop at explicit `<event action="confirm">` blocks)
|
|
29
|
+
|
|
30
|
+
# Feature Designer Orchestration
|
|
31
|
+
|
|
32
|
+
Feature Designer 的核心编排技能,负责:
|
|
33
|
+
|
|
34
|
+
1. **Stage Gate Verification** - 验证 PRD 阶段已完成确认
|
|
35
|
+
2. **Feature List Loading** - 从 .prd-feature-list.json 加载功能清单
|
|
36
|
+
3. **Feature Analysis Orchestration** - 协调功能分析(单个直接调用,多个分发 Worker)
|
|
37
|
+
4. **Feature Design Orchestration** - 协调功能规格设计
|
|
38
|
+
5. **API Contract Generation** - 生成 API 契约文档
|
|
39
|
+
6. **Joint Confirmation** - 汇总确认所有设计产出
|
|
40
|
+
|
|
41
|
+
## Invocation Method
|
|
42
|
+
|
|
43
|
+
**CRITICAL**: This skill is loaded directly by Feature Designer Agent — do NOT invoke via Worker Agent.
|
|
44
|
+
|
|
45
|
+
```xml
|
|
46
|
+
<block type="task" action="run-skill" desc="Feature Designer orchestration workflow">
|
|
47
|
+
<field name="skill">speccrew-feature-designer-orchestration</field>
|
|
48
|
+
</block>
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
## Input Parameters
|
|
52
|
+
|
|
53
|
+
| Parameter | Type | Required | Description |
|
|
54
|
+
|-----------|------|----------|-------------|
|
|
55
|
+
| `prd_path` | string | Yes | PRD 文档目录路径 |
|
|
56
|
+
| `iteration_path` | string | Yes | 当前迭代目录路径 |
|
|
57
|
+
| `workspace_root` | string | Yes | speccrew-workspace 根目录路径 |
|
|
58
|
+
| `frontend_platforms` | array | No | 前端平台列表(从 techs-manifest 读取) |
|
|
59
|
+
|
|
60
|
+
## Output
|
|
61
|
+
|
|
62
|
+
- `status` - 执行状态 (success / partial / failed)
|
|
63
|
+
- `feature_specs` - 生成的功能规格文件列表
|
|
64
|
+
- `api_contracts` - 生成的 API 契约文件列表
|
|
65
|
+
- `workflow_stage` - 当前工作流阶段状态
|
|
66
|
+
- `next_agent` - 下一步建议的 Agent
|
|
67
|
+
|
|
68
|
+
---
|
|
69
|
+
|
|
70
|
+
## AgentFlow Definition
|
|
71
|
+
|
|
72
|
+
<!-- @agentflow: workflow.agentflow.xml -->
|
|
73
|
+
|
|
74
|
+
---
|
|
75
|
+
|
|
76
|
+
## CONTINUOUS EXECUTION RULES
|
|
77
|
+
|
|
78
|
+
This skill MUST execute tasks continuously without unnecessary interruptions.
|
|
79
|
+
|
|
80
|
+
### FORBIDDEN Interruptions
|
|
81
|
+
|
|
82
|
+
1. DO NOT ask user "Should I continue?" after completing a subtask
|
|
83
|
+
2. DO NOT suggest "Let me split this into batches" or "Let's do this in parts"
|
|
84
|
+
3. DO NOT pause to list what you plan to do next — just do it
|
|
85
|
+
4. DO NOT ask for confirmation before generating output files
|
|
86
|
+
5. DO NOT warn about "large number of files" — proceed with generation
|
|
87
|
+
6. DO NOT offer "Should I proceed with the remaining items?"
|
|
88
|
+
|
|
89
|
+
### When to Pause (ONLY these cases)
|
|
90
|
+
|
|
91
|
+
1. CHECKPOINT gates defined in workflow (user confirmation required by design)
|
|
92
|
+
2. Ambiguous requirements that genuinely need clarification
|
|
93
|
+
3. Unrecoverable errors that prevent further progress
|
|
94
|
+
4. Security-sensitive operations (e.g., deleting existing files)
|
|
95
|
+
|
|
96
|
+
### Worker Enforcement Rules
|
|
97
|
+
|
|
98
|
+
This agent is an **orchestrator/dispatcher**. When multiple Features exist, it MUST delegate all skill execution to `speccrew-task-worker` agents.
|
|
99
|
+
|
|
100
|
+
| Condition | Action | Tool |
|
|
101
|
+
|-----------|--------|------|
|
|
102
|
+
| 1 Feature | Direct skill invocation allowed | Skill tool |
|
|
103
|
+
| 2+ Features | **MUST** dispatch Workers | speccrew-task-worker via Agent tool |
|
|
104
|
+
|
|
105
|
+
### FORBIDDEN Actions (When Features ≥ 2)
|
|
106
|
+
|
|
107
|
+
1. ❌ DO NOT invoke `speccrew-fd-feature-analyze` skill directly
|
|
108
|
+
2. ❌ DO NOT invoke `speccrew-fd-feature-design` skill directly
|
|
109
|
+
3. ❌ DO NOT invoke `speccrew-fd-api-contract` skill directly
|
|
110
|
+
4. ❌ DO NOT generate `.feature-analysis.md` files yourself
|
|
111
|
+
5. ❌ DO NOT generate `.feature-spec.md` files yourself
|
|
112
|
+
6. ❌ DO NOT generate `.api-contract.md` files yourself
|
|
113
|
+
7. ❌ DO NOT create any document content as fallback if worker fails
|
|
114
|
+
|
|
115
|
+
### Name Lock Rule
|
|
116
|
+
|
|
117
|
+
After Phase 2 Feature List is confirmed, feature_name is immutable. All Skills MUST use the exact parameter value for output filenames. Name translation or substitution is FORBIDDEN.
|