speccrew 0.6.6 → 0.6.8
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 +25 -20
- package/.speccrew/agents/speccrew-product-manager.md +99 -47
- package/.speccrew/agents/speccrew-system-designer.md +33 -28
- package/.speccrew/agents/speccrew-system-developer.md +34 -29
- package/.speccrew/agents/speccrew-test-manager.md +47 -42
- package/.speccrew/skills/speccrew-knowledge-bizs-dispatch/SKILL.md +104 -69
- package/.speccrew/skills/speccrew-knowledge-bizs-identify-entries/SKILL.md +10 -4
- package/.speccrew/skills/speccrew-knowledge-bizs-init-features/SKILL.md +33 -24
- package/.speccrew/skills/speccrew-knowledge-bizs-init-features/scripts/generate-inventory.js +23 -6
- package/.speccrew/skills/speccrew-pm-knowledge-detector/SKILL.md +8 -4
- package/package.json +1 -1
- package/workspace-template/scripts/path-utils.js +134 -0
|
@@ -143,13 +143,18 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
|
|
|
143
143
|
|
|
144
144
|
## Phase 0: Workflow Progress Management
|
|
145
145
|
|
|
146
|
+
> **Path Variables** (provided by caller as absolute paths):
|
|
147
|
+
> - `workspace_path`: Absolute path to speccrew-workspace directory
|
|
148
|
+
> - `update_progress_script`: `{workspace_path}/scripts/update-progress.js`
|
|
149
|
+
> - `iterations_dir`: `{workspace_path}/iterations`
|
|
150
|
+
|
|
146
151
|
### Step 0.1: Stage Gate — Verify Upstream Completion
|
|
147
152
|
|
|
148
153
|
Before starting system design, verify that Feature Design stage is confirmed:
|
|
149
154
|
|
|
150
155
|
1. **Read WORKFLOW-PROGRESS.json overview**:
|
|
151
156
|
```bash
|
|
152
|
-
node
|
|
157
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/WORKFLOW-PROGRESS.json --overview
|
|
153
158
|
```
|
|
154
159
|
|
|
155
160
|
2. **Validate upstream stage**: Check `stages.02_feature_design.status == "confirmed"` in the output
|
|
@@ -160,7 +165,7 @@ Before starting system design, verify that Feature Design stage is confirmed:
|
|
|
160
165
|
- Read `02_feature_design.outputs` to get Feature Spec and API Contract paths
|
|
161
166
|
- Update stage status:
|
|
162
167
|
```bash
|
|
163
|
-
node
|
|
168
|
+
node {update_progress_script} update-workflow --file {iterations_dir}/{current}/WORKFLOW-PROGRESS.json --stage 03_system_design --status in_progress
|
|
164
169
|
```
|
|
165
170
|
|
|
166
171
|
### Step 0.2: Check Resume State (断点续传)
|
|
@@ -169,7 +174,7 @@ Check if there's existing progress to resume:
|
|
|
169
174
|
|
|
170
175
|
1. **Read checkpoints** (if file exists):
|
|
171
176
|
```bash
|
|
172
|
-
node
|
|
177
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/03.system-design/.checkpoints.json --checkpoints
|
|
173
178
|
```
|
|
174
179
|
|
|
175
180
|
2. **Determine resume point** based on passed checkpoints:
|
|
@@ -184,7 +189,7 @@ Check dispatch progress for parallel task execution:
|
|
|
184
189
|
|
|
185
190
|
1. **Read dispatch progress summary** (if file exists):
|
|
186
191
|
```bash
|
|
187
|
-
node
|
|
192
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --summary
|
|
188
193
|
```
|
|
189
194
|
|
|
190
195
|
2. **List task statuses**:
|
|
@@ -263,8 +268,8 @@ When user requests to start system design (and Phase 0 gates are passed):
|
|
|
263
268
|
|
|
264
269
|
Use Glob to find relevant documents in the current iteration:
|
|
265
270
|
|
|
266
|
-
- Feature Spec pattern: `
|
|
267
|
-
- API Contract pattern: `
|
|
271
|
+
- Feature Spec pattern: `{iterations_dir}/{current}/02.feature-design/*-feature-spec.md`
|
|
272
|
+
- API Contract pattern: `{iterations_dir}/{current}/02.feature-design/*-api-contract.md`
|
|
268
273
|
|
|
269
274
|
**文件命名格式说明**:
|
|
270
275
|
- **新格式**（细粒度 Feature）: 文件名以 Feature ID 开头，格式为 `{feature-id}-{feature-name}-feature-spec.md`
|
|
@@ -311,7 +316,7 @@ Use Glob to find relevant documents in the current iteration:
|
|
|
311
316
|
### 1.3 Check Existing System Design Documents
|
|
312
317
|
|
|
313
318
|
Check if system design documents already exist:
|
|
314
|
-
- Check path: `
|
|
319
|
+
- Check path: `{iterations_dir}/{current}/03.system-design/`
|
|
315
320
|
|
|
316
321
|
### 1.4 Present Design Scope to User
|
|
317
322
|
|
|
@@ -382,7 +387,7 @@ After user confirmation, load knowledge in the following order:
|
|
|
382
387
|
|
|
383
388
|
**Gate Check — Techs Knowledge Base Availability:**
|
|
384
389
|
|
|
385
|
-
1. Check if `
|
|
390
|
+
1. Check if `{workspace_path}/knowledges/techs/techs-manifest.json` exists
|
|
386
391
|
2. **IF NOT EXISTS** → STOP and report to user:
|
|
387
392
|
```
|
|
388
393
|
❌ TECHS KNOWLEDGE BASE NOT FOUND
|
|
@@ -399,7 +404,7 @@ After user confirmation, load knowledge in the following order:
|
|
|
399
404
|
→ END workflow (do not proceed to Phase 3)
|
|
400
405
|
3. **IF EXISTS** → Continue loading techs knowledge as below
|
|
401
406
|
|
|
402
|
-
1. Read `
|
|
407
|
+
1. Read `{workspace_path}/knowledges/techs/techs-manifest.json` to discover platforms
|
|
403
408
|
2. For each platform in manifest, load key techs knowledge:
|
|
404
409
|
- `knowledges/techs/{platform_id}/tech-stack.md`
|
|
405
410
|
- `knowledges/techs/{platform_id}/architecture.md`
|
|
@@ -422,8 +427,8 @@ After user confirmation, load knowledge in the following order:
|
|
|
422
427
|
| `feature_spec_paths` | All Feature Spec paths from Feature Registry | Feature Spec documents to analyze |
|
|
423
428
|
| `api_contract_paths` | All API Contract paths from Feature Registry | API Contract documents to analyze |
|
|
424
429
|
| `techs_knowledge_paths` | Platform knowledge paths loaded in Phase 2 | Technology stack knowledge per platform |
|
|
425
|
-
| `iteration_path` | `
|
|
426
|
-
| `output_path` | `
|
|
430
|
+
| `iteration_path` | `{iterations_dir}/{current}` | Current iteration directory |
|
|
431
|
+
| `output_path` | `{iterations_dir}/{current}/03.system-design/framework-evaluation.md` | Output report path |
|
|
427
432
|
|
|
428
433
|
**Invocation**: Call the skill directly (not via speccrew-task-worker — framework evaluation is a single coordinated task, not per-Feature).
|
|
429
434
|
|
|
@@ -498,7 +503,7 @@ Proceed to Phase 4? (确认/取消)
|
|
|
498
503
|
## Phase 4: Generate DESIGN-OVERVIEW.md (L1)
|
|
499
504
|
|
|
500
505
|
Create the top-level overview at:
|
|
501
|
-
`
|
|
506
|
+
`{iterations_dir}/{current}/03.system-design/DESIGN-OVERVIEW.md`
|
|
502
507
|
|
|
503
508
|
### Template Structure
|
|
504
509
|
|
|
@@ -628,7 +633,7 @@ Before dispatching, create or update dispatch tracking:
|
|
|
628
633
|
# Step 1: Write tasks JSON to temp file inside iteration directory
|
|
629
634
|
# Create .tasks-temp.json with the task array content
|
|
630
635
|
# Step 2: Initialize with --tasks-file
|
|
631
|
-
node
|
|
636
|
+
node {update_progress_script} init --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --stage 03_system_design --tasks-file {iterations_dir}/{current}/03.system-design/.tasks-temp.json
|
|
632
637
|
# Step 3: Delete .tasks-temp.json after successful init
|
|
633
638
|
```
|
|
634
639
|
|
|
@@ -645,7 +650,7 @@ Before dispatching, create or update dispatch tracking:
|
|
|
645
650
|
2. **Check existing progress** (from Step 0.3) — skip `completed` tasks
|
|
646
651
|
3. **Update status** to `in_progress` for tasks being dispatched:
|
|
647
652
|
```bash
|
|
648
|
-
node
|
|
653
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
|
|
649
654
|
```
|
|
650
655
|
|
|
651
656
|
### 5.3 Single Feature Spec + Single Platform
|
|
@@ -654,7 +659,7 @@ When there is only one Feature Spec and one platform:
|
|
|
654
659
|
|
|
655
660
|
1. **Update task status to `in_progress`**:
|
|
656
661
|
```bash
|
|
657
|
-
node
|
|
662
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
|
|
658
663
|
```
|
|
659
664
|
|
|
660
665
|
2. Call skill directly with parameters:
|
|
@@ -672,11 +677,11 @@ When there is only one Feature Spec and one platform:
|
|
|
672
677
|
3. **Parse Task Completion Report** from skill output:
|
|
673
678
|
- If `Status: SUCCESS`:
|
|
674
679
|
```bash
|
|
675
|
-
node
|
|
680
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status completed --output "{output_path}"
|
|
676
681
|
```
|
|
677
682
|
- If `Status: FAILED`:
|
|
678
683
|
```bash
|
|
679
|
-
node
|
|
684
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "{error_message}"
|
|
680
685
|
```
|
|
681
686
|
|
|
682
687
|
### 5.4 Parallel Execution (Feature × Platform)
|
|
@@ -707,7 +712,7 @@ Each worker receives:
|
|
|
707
712
|
|
|
708
713
|
**Before dispatch**: Update each task status to `in_progress`:
|
|
709
714
|
```bash
|
|
710
|
-
node
|
|
715
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status in_progress
|
|
711
716
|
```
|
|
712
717
|
|
|
713
718
|
**Parallel execution example** (2 features × 3 platforms = 6 workers):
|
|
@@ -726,11 +731,11 @@ After each worker completes, parse its **Task Completion Report** and update:
|
|
|
726
731
|
|
|
727
732
|
- On SUCCESS:
|
|
728
733
|
```bash
|
|
729
|
-
node
|
|
734
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status completed --output "{output_path}"
|
|
730
735
|
```
|
|
731
736
|
- On FAILED:
|
|
732
737
|
```bash
|
|
733
|
-
node
|
|
738
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "{error_message}"
|
|
734
739
|
```
|
|
735
740
|
|
|
736
741
|
Wait for all workers to complete before proceeding to Phase 6.
|
|
@@ -745,7 +750,7 @@ When any platform design worker reports failure:
|
|
|
745
750
|
|
|
746
751
|
2. **Update DISPATCH-PROGRESS.json**:
|
|
747
752
|
```bash
|
|
748
|
-
node
|
|
753
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/03.system-design/DISPATCH-PROGRESS.json --task-id {task_id} --status failed --error "{error_message}"
|
|
749
754
|
```
|
|
750
755
|
|
|
751
756
|
3. **Continue batch**: Do NOT stop entire batch for single failure. Complete remaining workers.
|
|
@@ -891,14 +896,14 @@ After user confirms:
|
|
|
891
896
|
|
|
892
897
|
1. **Write checkpoints**:
|
|
893
898
|
```bash
|
|
894
|
-
node
|
|
895
|
-
node
|
|
896
|
-
node
|
|
899
|
+
node {update_progress_script} write-checkpoint --file {iterations_dir}/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint framework_evaluation --passed true
|
|
900
|
+
node {update_progress_script} write-checkpoint --file {iterations_dir}/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint design_overview --passed true
|
|
901
|
+
node {update_progress_script} write-checkpoint --file {iterations_dir}/{current}/03.system-design/.checkpoints.json --stage 03_system_design --checkpoint joint_confirmation --passed true
|
|
897
902
|
```
|
|
898
903
|
|
|
899
904
|
2. **Update WORKFLOW-PROGRESS.json**:
|
|
900
905
|
```bash
|
|
901
|
-
node
|
|
906
|
+
node {update_progress_script} update-workflow --file {iterations_dir}/{current}/WORKFLOW-PROGRESS.json --stage 03_system_design --status confirmed --output "DESIGN-OVERVIEW.md, platform-indexes, module-designs"
|
|
902
907
|
```
|
|
903
908
|
|
|
904
909
|
3. **Designs become baseline** for Dev phase
|
|
@@ -907,9 +912,9 @@ After user confirms:
|
|
|
907
912
|
|
|
908
913
|
| Deliverable | Path | Template |
|
|
909
914
|
|-------------|------|----------|
|
|
910
|
-
| Design Overview | `
|
|
911
|
-
| Platform Index | `
|
|
912
|
-
| Module Design | `
|
|
915
|
+
| Design Overview | `{iterations_dir}/{number}-{type}-{name}/03.system-design/DESIGN-OVERVIEW.md` | Inline (see Phase 4) |
|
|
916
|
+
| Platform Index | `{iterations_dir}/{number}-{type}-{name}/03.system-design/{platform_id}/INDEX.md` | `speccrew-sd-frontend/templates/INDEX-TEMPLATE.md`, `speccrew-sd-backend/templates/INDEX-TEMPLATE.md`, `speccrew-sd-mobile/templates/INDEX-TEMPLATE.md`, or `speccrew-sd-desktop/templates/INDEX-TEMPLATE.md` |
|
|
917
|
+
| Module Design | `{iterations_dir}/{number}-{type}-{name}/03.system-design/{platform_id}/{feature-id}-{feature-name}-design.md` | `speccrew-sd-frontend/templates/SD-FRONTEND-TEMPLATE.md`, `speccrew-sd-backend/templates/SD-BACKEND-TEMPLATE.md`, `speccrew-sd-mobile/templates/SD-MOBILE-TEMPLATE.md`, or `speccrew-sd-desktop/templates/SD-DESKTOP-TEMPLATE.md` |
|
|
913
918
|
|
|
914
919
|
**输出文件命名规则**:
|
|
915
920
|
|
|
@@ -177,13 +177,18 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
|
|
|
177
177
|
|
|
178
178
|
## Step 0: Workflow Progress Management
|
|
179
179
|
|
|
180
|
+
> **Path Variables** (provided by caller as absolute paths):
|
|
181
|
+
> - `workspace_path`: Absolute path to speccrew-workspace directory
|
|
182
|
+
> - `update_progress_script`: `{workspace_path}/scripts/update-progress.js`
|
|
183
|
+
> - `iterations_dir`: `{workspace_path}/iterations`
|
|
184
|
+
|
|
180
185
|
### Phase 0.1: Stage Gate — Verify Upstream Completion
|
|
181
186
|
|
|
182
187
|
Before starting development, verify upstream stage completion:
|
|
183
188
|
|
|
184
189
|
1. **Read WORKFLOW-PROGRESS.json overview**:
|
|
185
190
|
```bash
|
|
186
|
-
node
|
|
191
|
+
node {update_progress_script} read --file {workspace_path}/WORKFLOW-PROGRESS.json --overview
|
|
187
192
|
```
|
|
188
193
|
|
|
189
194
|
2. **Verify System Design stage status**:
|
|
@@ -193,7 +198,7 @@ Before starting development, verify upstream stage completion:
|
|
|
193
198
|
|
|
194
199
|
3. **Update Development stage status**:
|
|
195
200
|
```bash
|
|
196
|
-
node
|
|
201
|
+
node {update_progress_script} update-workflow --file {workspace_path}/WORKFLOW-PROGRESS.json --stage 04_development --status in_progress
|
|
197
202
|
```
|
|
198
203
|
|
|
199
204
|
### Phase 0.2: Check Resume State
|
|
@@ -202,7 +207,7 @@ Check for existing checkpoint state to support resume:
|
|
|
202
207
|
|
|
203
208
|
1. **Read checkpoints** (if file exists):
|
|
204
209
|
```bash
|
|
205
|
-
node
|
|
210
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/04.development/.checkpoints.json --checkpoints
|
|
206
211
|
```
|
|
207
212
|
|
|
208
213
|
2. **Determine resume point based on passed checkpoints**:
|
|
@@ -221,7 +226,7 @@ Check for existing dispatch progress to support module-level retry:
|
|
|
221
226
|
|
|
222
227
|
1. **Read dispatch progress summary** (if file exists):
|
|
223
228
|
```bash
|
|
224
|
-
node
|
|
229
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --summary
|
|
225
230
|
```
|
|
226
231
|
|
|
227
232
|
2. **Parse the output** to get counts:
|
|
@@ -311,8 +316,8 @@ When user requests to start development:
|
|
|
311
316
|
|
|
312
317
|
Use Glob to find the design documents in the current iteration:
|
|
313
318
|
|
|
314
|
-
- Design Overview pattern: `
|
|
315
|
-
- Platform design pattern: `
|
|
319
|
+
- Design Overview pattern: `{iterations_dir}/{current}/03.system-design/DESIGN-OVERVIEW.md`
|
|
320
|
+
- Platform design pattern: `{iterations_dir}/{current}/03.system-design/{platform_id}/INDEX.md`
|
|
316
321
|
|
|
317
322
|
### 1.2 Read Design Overview
|
|
318
323
|
|
|
@@ -341,7 +346,7 @@ For each platform_id identified:
|
|
|
341
346
|
|
|
342
347
|
**Gate Check — Techs Knowledge Base Availability:**
|
|
343
348
|
|
|
344
|
-
1. Check if `
|
|
349
|
+
1. Check if `{workspace_path}/knowledges/techs/techs-manifest.json` exists
|
|
345
350
|
2. **IF NOT EXISTS** → STOP and report to user:
|
|
346
351
|
```
|
|
347
352
|
❌ TECHS KNOWLEDGE BASE NOT FOUND
|
|
@@ -407,7 +412,7 @@ Verify required services are accessible:
|
|
|
407
412
|
If all pre-checks pass:
|
|
408
413
|
1. **Write checkpoint**:
|
|
409
414
|
```bash
|
|
410
|
-
node
|
|
415
|
+
node {update_progress_script} write-checkpoint --file {iterations_dir}/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint environment_precheck --passed true --description "Runtime environment verification"
|
|
411
416
|
```
|
|
412
417
|
|
|
413
418
|
### 3.5 Pre-check Failure Handling
|
|
@@ -470,12 +475,12 @@ Each Worker MUST list all generated scripts in their Task Record under a "Genera
|
|
|
470
475
|
Before dispatching tasks, create or read dispatch progress file:
|
|
471
476
|
|
|
472
477
|
1. **Check if DISPATCH-PROGRESS.json exists**:
|
|
473
|
-
- Path: `
|
|
478
|
+
- Path: `{iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json`
|
|
474
479
|
- If exists, read summary to determine resume state
|
|
475
480
|
|
|
476
481
|
2. **If not exists — Create fresh dispatch progress**:
|
|
477
482
|
```bash
|
|
478
|
-
node
|
|
483
|
+
node {update_progress_script} init --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --stage 04_development --tasks-file <tasks_json_path>
|
|
479
484
|
```
|
|
480
485
|
Where `<tasks_json_path>` contains the task list built from Step 1.3:
|
|
481
486
|
```json
|
|
@@ -500,10 +505,10 @@ Before dispatching tasks, create or read dispatch progress file:
|
|
|
500
505
|
```bash
|
|
501
506
|
# Write tasks to temp file, then use --tasks-file
|
|
502
507
|
# Create .tasks-temp.json with task array content inside iteration directory
|
|
503
|
-
node
|
|
504
|
-
--file
|
|
508
|
+
node {update_progress_script} init \
|
|
509
|
+
--file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json \
|
|
505
510
|
--stage 04_development \
|
|
506
|
-
--tasks-file
|
|
511
|
+
--tasks-file {iterations_dir}/{current}/04.development/.tasks-temp.json
|
|
507
512
|
# Delete .tasks-temp.json after successful init
|
|
508
513
|
```
|
|
509
514
|
|
|
@@ -641,7 +646,7 @@ for each platform_id:
|
|
|
641
646
|
**After user confirms**:
|
|
642
647
|
1. **Write checkpoint**:
|
|
643
648
|
```bash
|
|
644
|
-
node
|
|
649
|
+
node {update_progress_script} write-checkpoint --file {iterations_dir}/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint task_list_review --passed true --description "Development task list confirmed by user"
|
|
645
650
|
```
|
|
646
651
|
|
|
647
652
|
### 4.3 Dispatch Workers with Concurrency Limit
|
|
@@ -670,7 +675,7 @@ while pending is not empty or running is not empty:
|
|
|
670
675
|
|
|
671
676
|
// Update task status to "in_progress"
|
|
672
677
|
```bash
|
|
673
|
-
node
|
|
678
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_progress
|
|
674
679
|
```
|
|
675
680
|
|
|
676
681
|
// Dispatch speccrew-task-worker agent (NOT Skill tool directly)
|
|
@@ -697,13 +702,13 @@ while pending is not empty or running is not empty:
|
|
|
697
702
|
if report.status == "SUCCESS":
|
|
698
703
|
// Mark as in_review pending review verification
|
|
699
704
|
```bash
|
|
700
|
-
node
|
|
705
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_review --output "{report.output_files}"
|
|
701
706
|
```
|
|
702
707
|
Add task to review_queue for Phase 4.4
|
|
703
708
|
else:
|
|
704
709
|
// Even failed dev workers go to review for diagnosis
|
|
705
710
|
```bash
|
|
706
|
-
node
|
|
711
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_review --error "{report.error}"
|
|
707
712
|
```
|
|
708
713
|
Add task to review_queue for Phase 4.4
|
|
709
714
|
|
|
@@ -724,7 +729,7 @@ while pending is not empty or running is not empty:
|
|
|
724
729
|
After processing a batch of completed workers:
|
|
725
730
|
1. **Read current progress summary**:
|
|
726
731
|
```bash
|
|
727
|
-
node
|
|
732
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --summary
|
|
728
733
|
```
|
|
729
734
|
2. Present progress summary to user:
|
|
730
735
|
```
|
|
@@ -808,16 +813,16 @@ for each task in review_queue:
|
|
|
808
813
|
|
|
809
814
|
if review.verdict == "PASS":
|
|
810
815
|
```bash
|
|
811
|
-
node
|
|
816
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status completed --output "{review_report_path}"
|
|
812
817
|
```
|
|
813
818
|
elif review.verdict == "PARTIAL":
|
|
814
819
|
```bash
|
|
815
|
-
node
|
|
820
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status partial --output "{review_report_path}" --metadata "{review.redispatch_guidance}"
|
|
816
821
|
```
|
|
817
822
|
Add task to redispatch_queue
|
|
818
823
|
else: // FAIL
|
|
819
824
|
```bash
|
|
820
|
-
node
|
|
825
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status failed --error "{review.summary}" --error-category VALIDATION_ERROR
|
|
821
826
|
```
|
|
822
827
|
```
|
|
823
828
|
|
|
@@ -839,8 +844,8 @@ After all initial dev + review cycles complete for the current batch:
|
|
|
839
844
|
|
|
840
845
|
1. **Query partial/failed tasks:**
|
|
841
846
|
```bash
|
|
842
|
-
node
|
|
843
|
-
node
|
|
847
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --status partial
|
|
848
|
+
node {update_progress_script} read --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --status failed
|
|
844
849
|
```
|
|
845
850
|
|
|
846
851
|
2. **For each partial/failed task, re-dispatch a dev worker with:**
|
|
@@ -857,7 +862,7 @@ After all initial dev + review cycles complete for the current batch:
|
|
|
857
862
|
|
|
858
863
|
5. **Update counts after each cycle:**
|
|
859
864
|
```bash
|
|
860
|
-
node
|
|
865
|
+
node {update_progress_script} update-counts --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json
|
|
861
866
|
```
|
|
862
867
|
|
|
863
868
|
**Re-dispatch Flow:**
|
|
@@ -872,13 +877,13 @@ for each task in redispatch_queue:
|
|
|
872
877
|
if attempts > 3:
|
|
873
878
|
// Max attempts reached - mark as permanently failed
|
|
874
879
|
```bash
|
|
875
|
-
node
|
|
880
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status failed --error "Max re-dispatch attempts (3) exceeded" --metadata "{accumulated_errors}"
|
|
876
881
|
```
|
|
877
882
|
continue
|
|
878
883
|
|
|
879
884
|
// Update attempt count and reset to in_progress
|
|
880
885
|
```bash
|
|
881
|
-
node
|
|
886
|
+
node {update_progress_script} update-task --file {iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json --task-id {task.id} --status in_progress --metadata "{attempts: attempts, previous_review: review_report_path}"
|
|
882
887
|
```
|
|
883
888
|
|
|
884
889
|
// Dispatch dev worker with supplemental context
|
|
@@ -958,7 +963,7 @@ Present comprehensive report based on DISPATCH-PROGRESS.json:
|
|
|
958
963
|
### 6.1 Read Final Dispatch Progress
|
|
959
964
|
|
|
960
965
|
1. **Read DISPATCH-PROGRESS.json**:
|
|
961
|
-
- Path: `
|
|
966
|
+
- Path: `{iterations_dir}/{current}/04.development/DISPATCH-PROGRESS.json`
|
|
962
967
|
|
|
963
968
|
2. **Calculate final statistics**:
|
|
964
969
|
- Total: `tasks.length`
|
|
@@ -1066,12 +1071,12 @@ Delivery Report: {path}/delivery-report.md
|
|
|
1066
1071
|
|
|
1067
1072
|
1. **Update checkpoint**:
|
|
1068
1073
|
```bash
|
|
1069
|
-
node
|
|
1074
|
+
node {update_progress_script} write-checkpoint --file {iterations_dir}/{current}/04.development/.checkpoints.json --stage 04_development --checkpoint delivery_report --passed true --description "Final delivery report"
|
|
1070
1075
|
```
|
|
1071
1076
|
|
|
1072
1077
|
2. **Update WORKFLOW-PROGRESS.json**:
|
|
1073
1078
|
```bash
|
|
1074
|
-
node
|
|
1079
|
+
node {update_progress_script} update-workflow --file {workspace_path}/WORKFLOW-PROGRESS.json --stage 04_development --status confirmed --output "04.development/{platform_id}/{module}/"
|
|
1075
1080
|
```
|
|
1076
1081
|
|
|
1077
1082
|
3. **Confirm stage transition**: Report to user that development stage is complete and system is ready for testing phase.
|