@curdx/flow 2.0.4 → 2.0.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.
- package/.claude-plugin/plugin.json +1 -1
- package/agents/flow-architect.md +38 -18
- package/agents/flow-planner.md +32 -0
- package/agents/flow-product-designer.md +31 -0
- package/agents/flow-researcher.md +30 -0
- package/cli/install-companions.js +251 -0
- package/cli/install-curdx-plugin.js +102 -0
- package/cli/install-language.js +35 -0
- package/cli/install-next-steps.js +25 -0
- package/cli/install-options.js +9 -0
- package/cli/install-paths.js +39 -0
- package/cli/install-self-update.js +57 -0
- package/cli/install.js +33 -523
- package/commands/spec.md +48 -0
- package/package.json +1 -1
package/commands/spec.md
CHANGED
|
@@ -76,18 +76,66 @@ For each phase in the resolved list, dispatch a sub-agent via the `Task` tool:
|
|
|
76
76
|
Inputs: spec goal + one-line description from `.state.json`.
|
|
77
77
|
Output: `research.md` covering problem space, prior art (library candidates via `context7`), constraints, technical recommendation.
|
|
78
78
|
|
|
79
|
+
**Dispatch prompt prefix (MANDATORY)**:
|
|
80
|
+
```
|
|
81
|
+
CRITICAL OUTPUT PROTOCOL: Your FIRST action must be calling Write tool with the full research.md content. Do NOT explain, narrate, or preview. After Write succeeds, output EXACTLY 3 lines:
|
|
82
|
+
✓ research.md generated
|
|
83
|
+
Recommendations: N
|
|
84
|
+
Next: /curdx-flow:spec --phase=requirements
|
|
85
|
+
|
|
86
|
+
FORBIDDEN: explanations, summaries, findings lists. The file is the deliverable.
|
|
87
|
+
---
|
|
88
|
+
```
|
|
89
|
+
|
|
79
90
|
### requirements → `flow-product-designer`
|
|
80
91
|
Inputs: `research.md`.
|
|
81
92
|
Output: `requirements.md` with user stories (US-NN), acceptance criteria (AC-N.N), functional requirements (FR-NN), non-functional requirements (NFR-*).
|
|
82
93
|
|
|
94
|
+
**Dispatch prompt prefix (MANDATORY)**:
|
|
95
|
+
```
|
|
96
|
+
CRITICAL OUTPUT PROTOCOL: Your FIRST action must be calling Write tool with the full requirements.md content. Do NOT explain, narrate, or preview. After Write succeeds, output EXACTLY 4 lines:
|
|
97
|
+
✓ requirements.md generated
|
|
98
|
+
User stories: N
|
|
99
|
+
Functional requirements: N
|
|
100
|
+
Next: /curdx-flow:spec --phase=design
|
|
101
|
+
|
|
102
|
+
FORBIDDEN: explanations, summaries, US/AC lists. The file is the deliverable.
|
|
103
|
+
---
|
|
104
|
+
```
|
|
105
|
+
|
|
83
106
|
### design → `flow-architect`
|
|
84
107
|
Inputs: `research.md` + `requirements.md`.
|
|
85
108
|
Output: `design.md` with architecture decisions (AD-NN), component boundaries, data models, error-path design, mermaid diagrams (when they clarify). Uses `sequential-thinking` MCP proportional to the genuine tradeoff surface.
|
|
86
109
|
|
|
110
|
+
**Dispatch prompt prefix (MANDATORY)**:
|
|
111
|
+
```
|
|
112
|
+
CRITICAL OUTPUT PROTOCOL: Your FIRST action must be calling Write tool with the full design.md content. Do NOT explain, narrate, or preview. After Write succeeds, output EXACTLY 4 lines:
|
|
113
|
+
✓ design.md generated
|
|
114
|
+
Architecture decisions: N
|
|
115
|
+
Components: N
|
|
116
|
+
Next: /curdx-flow:spec --phase=tasks
|
|
117
|
+
|
|
118
|
+
FORBIDDEN: explanations, summaries, AD lists, tech stack lists, warnings. The file is the deliverable.
|
|
119
|
+
---
|
|
120
|
+
```
|
|
121
|
+
|
|
87
122
|
### tasks → `flow-planner`
|
|
88
123
|
Inputs: all three prior files + `.flow/PROJECT.md` tech stack.
|
|
89
124
|
Output: `tasks.md` — POC-First 5-phase decomposition with per-task Verify commands, multi-source coverage audit against FR/AC/AD/Research/Decisions.
|
|
90
125
|
|
|
126
|
+
**Dispatch prompt prefix (MANDATORY)**:
|
|
127
|
+
```
|
|
128
|
+
CRITICAL OUTPUT PROTOCOL: Your FIRST action must be calling Write tool with the full tasks.md content. Do NOT explain, narrate, or preview. After Write succeeds, output EXACTLY 5 lines:
|
|
129
|
+
✓ tasks.md generated
|
|
130
|
+
Total tasks: N
|
|
131
|
+
Coverage audit: PASS
|
|
132
|
+
Phases: 1-5
|
|
133
|
+
Next: /curdx-flow:implement
|
|
134
|
+
|
|
135
|
+
FORBIDDEN: explanations, summaries, task lists. The file is the deliverable.
|
|
136
|
+
---
|
|
137
|
+
```
|
|
138
|
+
|
|
91
139
|
After each phase completes successfully, update `.state.json`:
|
|
92
140
|
|
|
93
141
|
```json
|