specsmd 0.0.0-dev.62 → 0.0.0-dev.63
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.
|
@@ -24,10 +24,17 @@ When routed from Orchestrator or user invokes this agent:
|
|
|
24
24
|
2. Read `.specs-fire/state.yaml` for current state
|
|
25
25
|
3. **Compare and reconcile** - add any items on disk but not in state.yaml
|
|
26
26
|
4. Determine mode:
|
|
27
|
-
- **Active run exists** → Resume execution
|
|
28
|
-
- **Pending work items** →
|
|
27
|
+
- **Active run exists** → Resume execution (skip to run-execute)
|
|
28
|
+
- **Pending work items** → **MUST invoke run-plan skill FIRST** to present scope options
|
|
29
29
|
- **No pending work items AND no untracked files** → Route back to Planner
|
|
30
30
|
|
|
31
|
+
**CRITICAL**: When pending work items exist, you MUST invoke the run-plan skill to:
|
|
32
|
+
1. Present run scope options (single/batch/wide)
|
|
33
|
+
2. Let user choose how to group work items
|
|
34
|
+
3. THEN invoke run-execute with the chosen scope
|
|
35
|
+
|
|
36
|
+
DO NOT skip run-plan and go directly to run-execute.
|
|
37
|
+
|
|
31
38
|
**CRITICAL**: Do NOT skip the file system scan. New intents/work-items may exist on disk that aren't in state.yaml yet. The file system is the source of truth.
|
|
32
39
|
|
|
33
40
|
---
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "specsmd",
|
|
3
|
-
"version": "0.0.0-dev.
|
|
3
|
+
"version": "0.0.0-dev.63",
|
|
4
4
|
"description": "Multi-agent orchestration system for AI-native software development. Delivers AI-DLC, Agile, and custom SDLC flows as markdown-based agent systems.",
|
|
5
5
|
"main": "lib/installer.js",
|
|
6
6
|
"bin": {
|