speccrew 0.2.6 → 0.2.7
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.
|
@@ -195,6 +195,16 @@ If any pre-check fails:
|
|
|
195
195
|
|
|
196
196
|
## Step 4: Dispatch Per-Module Dev Skills
|
|
197
197
|
|
|
198
|
+
#### ⚠️ Stage 4 Directory Constraint
|
|
199
|
+
|
|
200
|
+
All development outputs MUST go under `iterations/{iter}/04.development/`.
|
|
201
|
+
- Task records: `04.development/{platform_id}/{module}-task.md`
|
|
202
|
+
- Review reports: `04.development/{platform_id}/{module}-review-report.md`
|
|
203
|
+
- Dispatch progress: `04.development/DISPATCH-PROGRESS.json`
|
|
204
|
+
- Checkpoints: `04.development/.checkpoints.json`
|
|
205
|
+
|
|
206
|
+
**FORBIDDEN directory names**: `04.dev-report/`, `04.dev-reports/`, `04.implementation/`, or any other variant.
|
|
207
|
+
|
|
198
208
|
> ⛔ **NO DIRECT CODING**: System Developer MUST NOT use file creation/editing tools to write application code. Every module implementation MUST be dispatched to a `speccrew-task-worker` agent running a dev skill (speccrew-dev-backend/frontend/mobile/desktop). System Developer's role in this phase is EXCLUSIVELY: task list creation, worker dispatch, progress tracking, and review coordination.
|
|
199
209
|
|
|
200
210
|
> **IMPORTANT**: Dispatch `speccrew-task-worker` agents (via Agent tool) for parallel module development. Do NOT call dev skills directly — each module MUST run in an independent Worker Agent for progress visibility and error isolation.
|
|
@@ -16,7 +16,7 @@ tools: Read, Grep, Glob
|
|
|
16
16
|
| Parameter | Required | Description |
|
|
17
17
|
|-----------|----------|-------------|
|
|
18
18
|
| `design_doc_path` | Yes | Path to module design document (e.g., `03.system-design/module-designs/backend-spring/M6-employee-design.md`) |
|
|
19
|
-
| `implementation_report_path` | Yes | Path to development report (e.g., `04.
|
|
19
|
+
| `implementation_report_path` | Yes | Path to development report (e.g., `04.development/backend-spring/M6-employee-implementation-report.md`) |
|
|
20
20
|
| `source_root` | Yes | Root directory of source code to review |
|
|
21
21
|
| `platform_id` | Yes | Platform identifier (backend-spring/web-vue/mobile-uniapp/desktop-tauri) |
|
|
22
22
|
| `api_contract_path` | No | Path to API contract file for endpoint validation |
|
package/package.json
CHANGED
|
@@ -102,6 +102,21 @@ iterations/
|
|
|
102
102
|
| 系统设计 | `03.system-design/` | 详细设计、数据库设计、接口设计 |
|
|
103
103
|
| 开发 | `04.development/` | 代码实现、开发日志、技术债记录 |
|
|
104
104
|
| 测试 | `05.test/` | 测试用例、测试报告 |
|
|
105
|
+
|
|
106
|
+
#### Stage 4 详细目录结构 (`04.development/`)
|
|
107
|
+
|
|
108
|
+
```
|
|
109
|
+
04.development/
|
|
110
|
+
├── .checkpoints.json # Stage progress checkpoints
|
|
111
|
+
├── DISPATCH-PROGRESS.json # Task dispatch and execution tracking
|
|
112
|
+
├── {platform_id}/ # Grouped by platform (e.g., backend-spring, web-vue)
|
|
113
|
+
│ ├── {module}-task.md # Development task record (created by Dev Skill)
|
|
114
|
+
│ └── {module}-review-report.md # Code review report (created by Review Skill)
|
|
115
|
+
└── delivery-report.md # Final delivery summary
|
|
116
|
+
```
|
|
117
|
+
|
|
118
|
+
> ⚠️ **MANDATORY**: All Stage 4 outputs MUST use `04.development/` as the top-level directory.
|
|
119
|
+
> The following variants are **FORBIDDEN**: `04.dev-report/`, `04.dev-reports/`, `04.implementation/`, or any other `04.*` name.
|
|
105
120
|
| 交付 | `06.delivery/` | 部署文档、验收报告、交付清单 |
|
|
106
121
|
```
|
|
107
122
|
|