speccrew 0.7.28 → 0.7.29
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.
|
@@ -143,6 +143,19 @@ This agent MUST execute tasks continuously without unnecessary interruptions.
|
|
|
143
143
|
2. **FORBIDDEN: Manual JSON creation** — DO NOT use `create_file` or `write` to create progress/checkpoint JSON files. ALWAYS use the appropriate `update-progress.js` command.
|
|
144
144
|
3. **FORBIDDEN: Timestamp parameters** — DO NOT pass `--started-at`, `--completed-at`, or `--confirmed-at` parameters to `update-progress.js` commands. These parameters are deprecated.
|
|
145
145
|
|
|
146
|
+
## update-progress.js Command Reference
|
|
147
|
+
|
|
148
|
+
| Command | Purpose | Key Parameters |
|
|
149
|
+
|---------|---------|----------------|
|
|
150
|
+
| `init` | Initialize DISPATCH-PROGRESS.json | `--file`, `--stage`, `--tasks-file` (recommended) or `--tasks` |
|
|
151
|
+
| `read` | Query progress status | `--file`, `--summary`, `--checkpoints`, `--overview`, `--task-id`, `--status` |
|
|
152
|
+
| `update-task` | Mark worker completion | `--file`, `--task-id`, `--status`, `--output`, `--error` |
|
|
153
|
+
| `write-checkpoint` | Mark phase checkpoint | `--file`, `--stage`, `--checkpoint`, `--passed`, `--description` (optional) |
|
|
154
|
+
| `update-workflow` | Update workflow stage | `--file`, `--stage`, `--status`, `--output` (optional) |
|
|
155
|
+
| `update-counts` | Recalculate counts | `--file` |
|
|
156
|
+
|
|
157
|
+
> **Note**: Use `--tasks-file` instead of `--tasks` on Windows PowerShell to avoid JSON parsing issues.
|
|
158
|
+
|
|
146
159
|
# Workflow
|
|
147
160
|
|
|
148
161
|
## AgentFlow Definition
|
|
@@ -346,9 +359,12 @@ node {update_progress_script} write-checkpoint `
|
|
|
346
359
|
--file {iterations_dir}/{iteration}/02.feature-design/.checkpoints.json `
|
|
347
360
|
--stage 02_feature_design `
|
|
348
361
|
--checkpoint function_decomposition `
|
|
349
|
-
--
|
|
362
|
+
--passed true `
|
|
363
|
+
--description "Feature decomposition confirmed: N features across M modules"
|
|
350
364
|
```
|
|
351
365
|
|
|
366
|
+
> **Note**: Use `--passed` and `--description` for write-checkpoint. The `--data` parameter is NOT supported by update-progress.js.
|
|
367
|
+
|
|
352
368
|
**Feature status values:**
|
|
353
369
|
- `pending`: Not started
|
|
354
370
|
- `in_progress`: Worker dispatched
|
|
@@ -411,6 +427,67 @@ When involving related business domains, read `{workspace_path}/knowledges/bizs/
|
|
|
411
427
|
> 6. **Intermediate artifacts are MANDATORY.** .feature-analysis.md must exist before Phase 3b.
|
|
412
428
|
> 7. **Feature name is LOCKED after Phase 2 confirmation.** All Worker dispatch parameters MUST use the exact `feature_name` from `.checkpoints.json`. DO NOT derive, translate, or modify feature names at any point after the Feature List is confirmed.
|
|
413
429
|
|
|
430
|
+
### Prepare Task List for Dispatch
|
|
431
|
+
|
|
432
|
+
> ⚠️ **CRITICAL: Two Different File Formats**
|
|
433
|
+
>
|
|
434
|
+
> The `.prd-feature-list.json` and `init --tasks-file` expect DIFFERENT formats. Do NOT use one in place of the other.
|
|
435
|
+
|
|
436
|
+
#### `.prd-feature-list.json` — Feature Metadata Registry
|
|
437
|
+
|
|
438
|
+
This file is generated by PM Agent and contains the complete feature metadata with nested structure:
|
|
439
|
+
|
|
440
|
+
```json
|
|
441
|
+
{
|
|
442
|
+
"modules": [
|
|
443
|
+
{
|
|
444
|
+
"module_id": "M1-System",
|
|
445
|
+
"module_name": "System Management",
|
|
446
|
+
"features": [
|
|
447
|
+
{
|
|
448
|
+
"feature_id": "F-SYS-01",
|
|
449
|
+
"feature_name": "Account Login",
|
|
450
|
+
"feature_type": "Page+API",
|
|
451
|
+
"dependencies": []
|
|
452
|
+
}
|
|
453
|
+
]
|
|
454
|
+
}
|
|
455
|
+
]
|
|
456
|
+
}
|
|
457
|
+
```
|
|
458
|
+
|
|
459
|
+
- **Purpose**: Source of truth for feature metadata (names, types, dependencies)
|
|
460
|
+
- **Structure**: Nested `modules > features` array
|
|
461
|
+
- **Used by**: Agent reads this to understand feature breakdown
|
|
462
|
+
- **NOT for**: Direct use with `update-progress.js init` command
|
|
463
|
+
|
|
464
|
+
#### `.tasks-temp.json` — Flat Task Array for init Command
|
|
465
|
+
|
|
466
|
+
The `update-progress.js init --tasks-file` expects a **flat array** of task IDs:
|
|
467
|
+
|
|
468
|
+
```json
|
|
469
|
+
[
|
|
470
|
+
{"id": "F-SYS-01"},
|
|
471
|
+
{"id": "F-MEMBER-01"},
|
|
472
|
+
{"id": "F-CRM-01"}
|
|
473
|
+
]
|
|
474
|
+
```
|
|
475
|
+
|
|
476
|
+
- **Purpose**: Initialize DISPATCH-PROGRESS.json task list
|
|
477
|
+
- **Structure**: Flat array with `id` field only
|
|
478
|
+
- **Used by**: `update-progress.js init --tasks-file <path>`
|
|
479
|
+
- **Naming**: Recommend `.tasks-temp.json` (delete after init)
|
|
480
|
+
|
|
481
|
+
#### Conversion Step
|
|
482
|
+
|
|
483
|
+
Before initializing DISPATCH-PROGRESS.json, extract feature IDs from `.prd-feature-list.json`:
|
|
484
|
+
|
|
485
|
+
1. Read `.prd-feature-list.json`
|
|
486
|
+
2. Flatten `modules[].features[].feature_id` into array
|
|
487
|
+
3. Write `[{"id": "F-XXX"}, ...]` to `.tasks-temp.json`
|
|
488
|
+
4. Run `update-progress.js init --tasks-file .tasks-temp.json`
|
|
489
|
+
5. Delete `.tasks-temp.json`
|
|
490
|
+
|
|
414
491
|
---
|
|
415
492
|
|
|
416
493
|
### Phase 3a: Analyze — Function Decomposition
|