speccrew 0.5.18 → 0.6.0

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,8 +20,9 @@ SpecCrew-workspace/
20
20
  │ ├── 03.system-design/ # 系统设计
21
21
  │ ├── 04.development/ # 开发阶段
22
22
  │ │ └── tech-debt/ # 技术债记录(统一目录)
23
- │ ├── 05.test/ # 测试阶段
24
- └── 06.delivery/ # 交付阶段
23
+ │ ├── 05.deployment/ # 部署阶段
24
+ ├── 06.system-test/ # 系统测试阶段
25
+ │ └── 07.delivery/ # 交付阶段
25
26
 
26
27
  ├── iteration-archives/ # 迭代归档
27
28
  │ └── {序号}-{类型}-{名称}-{日期}/ # 如 001-feature-order-20260322
@@ -85,8 +86,9 @@ iterations/
85
86
  │ ├── 03.system-design/ # 系统设计
86
87
  │ ├── 04.development/ # 开发阶段
87
88
  │ │ └── tech-debt/ # 技术债记录(统一目录)
88
- │ ├── 05.test/ # 测试阶段
89
- └── 06.delivery/ # 交付阶段
89
+ │ ├── 05.deployment/ # 部署阶段
90
+ ├── 06.system-test/ # 系统测试阶段
91
+ │ └── 07.delivery/ # 交付阶段
90
92
 
91
93
  └── 002-bugfix-payment/ # 支付修复迭代(后启动)
92
94
  └── ...
@@ -101,7 +103,8 @@ iterations/
101
103
  | 特性设计 | `02.feature-design/` | 特性规格、API 契约、交互设计 |
102
104
  | 系统设计 | `03.system-design/` | 详细设计、数据库设计、接口设计 |
103
105
  | 开发 | `04.development/` | 代码实现、开发日志、技术债记录 |
104
- | 测试 | `05.test/` | 测试用例、测试报告 |
106
+ | 部署 | `05.deployment/` | 部署配置、部署日志 |
107
+ | 系统测试 | `06.system-test/` | 测试用例、测试报告 |
105
108
 
106
109
  #### Stage 4 详细目录结构 (`04.development/`)
107
110
 
@@ -117,7 +120,62 @@ iterations/
117
120
 
118
121
  > ⚠️ **MANDATORY**: All Stage 4 outputs MUST use `04.development/` as the top-level directory.
119
122
  > The following variants are **FORBIDDEN**: `04.dev-report/`, `04.dev-reports/`, `04.implementation/`, or any other `04.*` name.
120
- | 交付 | `06.delivery/` | 部署文档、验收报告、交付清单 |
123
+
124
+ #### Stage 5 详细目录结构 (`05.deployment/`)
125
+
126
+ ```
127
+ 05.deployment/
128
+ ├── .checkpoints.json # Stage progress checkpoints
129
+ ├── DISPATCH-PROGRESS.json # Task dispatch and execution tracking
130
+ ├── {platform_id}/ # Grouped by platform
131
+ │ ├── deployment-plan.md # Deployment plan for platform
132
+ │ └── deployment-log.md # Deployment execution log
133
+ └── delivery-report.md # Deployment completion report
134
+ ```
135
+
136
+ #### Stage 6 详细目录结构 (`06.system-test/`)
137
+
138
+ ```
139
+ 06.system-test/
140
+ ├── .checkpoints.json # Stage progress checkpoints
141
+ ├── DISPATCH-PROGRESS.json # Task dispatch and execution tracking
142
+ ├── cases/ # Test case documents
143
+ │ └── {platform_id}/
144
+ │ └── [feature]-test-cases.md
145
+ ├── code/ # Test code plans
146
+ │ └── {platform_id}/
147
+ │ └── [feature]-test-code-plan.md
148
+ ├── results/ # Test execution results
149
+ │ └── {platform_id}/
150
+ │ └── [feature]-test-execution-results.md
151
+ ├── reports/ # Test reports
152
+ │ └── [feature]-test-report.md
153
+ └── bugs/ # Bug reports
154
+ └── [feature]-bug-{序号}.md
155
+ ```
156
+
157
+ #### Stage 7 详细目录结构 (`07.delivery/`)
158
+
159
+ ```
160
+ 07.delivery/
161
+ ├── .checkpoints.json # Stage progress checkpoints
162
+ ├── deployment-guide.md # Deployment guide
163
+ ├── acceptance-report.md # Acceptance report
164
+ └── delivery-checklist.md # Delivery checklist
165
+ ```
166
+
167
+ **迭代阶段说明**:
168
+
169
+ | 阶段 | 目录 | 说明 |
170
+ |------|------|------|
171
+ | 原始需求 | `00.docs/` | 用户需求的原始文档,保持原样 |
172
+ | 产品需求 | `01.product-requirement/` | 产品需求文档,需求分析和规格说明 |
173
+ | 特性设计 | `02.feature-design/` | 特性规格、API 契约、交互设计 |
174
+ | 系统设计 | `03.system-design/` | 详细设计、数据库设计、接口设计 |
175
+ | 开发 | `04.development/` | 代码实现、开发日志、技术债记录 |
176
+ | 部署 | `05.deployment/` | 部署配置、部署日志 |
177
+ | 系统测试 | `06.system-test/` | 测试用例、测试报告 |
178
+ | 交付 | `07.delivery/` | 部署文档、验收报告、交付清单 |
121
179
  ```
122
180
 
123
181
  **迭代命名规范**:
@@ -330,4 +388,4 @@ techs/
330
388
  1. **迭代与知识分离**:`iterations/` 存放单次迭代产出,`knowledges/` 存放跨迭代共享知识
331
389
  2. **元数据集中管理**:诊断报告、同步状态统一放在 `knowledges/base/`
332
390
  3. **架构知识合并**:架构约定合并到 `techs/{platform}/architecture.md`,减少目录层级
333
- 4. **阶段目录有序**:迭代阶段使用数字前缀(00.docs ~ 06.delivery),便于排序和理解
391
+ 4. **阶段目录有序**:迭代阶段使用数字前缀(00.docs ~ 07.delivery),便于排序和理解