openmatrix 0.2.31 → 0.2.34
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/README.md +154 -154
- package/dist/cli/commands/approve.js +35 -1
- package/dist/cli/commands/auto.js +2 -2
- package/dist/cli/commands/check-gitignore.js +34 -30
- package/dist/cli/commands/check.js +1 -1
- package/dist/cli/commands/complete.js +35 -7
- package/dist/cli/commands/debug.js +2 -1
- package/dist/cli/commands/deploy.js +1 -1
- package/dist/cli/commands/install-skills.js +3 -0
- package/dist/cli/commands/meeting.js +37 -1
- package/dist/cli/commands/report.js +1 -1
- package/dist/cli/commands/resume.js +35 -1
- package/dist/cli/commands/retry.js +130 -56
- package/dist/cli/commands/start.js +1 -1
- package/dist/cli/commands/status.js +32 -29
- package/dist/cli/commands/step.js +4 -1
- package/dist/orchestrator/ai-reviewer.d.ts +5 -0
- package/dist/orchestrator/ai-reviewer.js +9 -2
- package/dist/orchestrator/context-collector.js +17 -5
- package/dist/orchestrator/executor.d.ts +8 -0
- package/dist/orchestrator/executor.js +24 -5
- package/dist/orchestrator/phase-executor.d.ts +4 -0
- package/dist/orchestrator/phase-executor.js +21 -4
- package/dist/storage/file-store.js +8 -0
- package/dist/storage/state-manager.js +52 -19
- package/dist/test/generator.js +113 -113
- package/dist/utils/error-handler.d.ts +18 -0
- package/dist/utils/error-handler.js +32 -0
- package/dist/utils/worktree-sync.js +24 -3
- package/package.json +61 -61
- package/skills/auto.md +410 -413
- package/skills/brainstorm.md +19 -12
- package/skills/debug.md +694 -691
- package/skills/deploy.md +658 -658
- package/skills/feature.md +713 -686
- package/skills/{SKILL.md → openmatrix-overview.md} +52 -53
- package/skills/plan.md +298 -296
- package/skills/report.md +9 -5
- package/skills/resume.md +292 -287
- package/skills/start.md +32 -20
- package/skills/status.md +5 -4
- package/skills/test.md +875 -875
- package/dist/agents/base-agent.d.ts +0 -46
- package/dist/agents/base-agent.js +0 -17
- package/dist/cli/commands/analyze.d.ts +0 -2
- package/dist/cli/commands/analyze.js +0 -50
- package/dist/orchestrator/smart-question-analyzer.d.ts +0 -90
- package/dist/orchestrator/smart-question-analyzer.js +0 -512
package/skills/brainstorm.md
CHANGED
|
@@ -51,7 +51,7 @@ description: "Use when the user wants to explore requirements, design alternativ
|
|
|
51
51
|
|
|
52
52
|
<process>
|
|
53
53
|
|
|
54
|
-
##
|
|
54
|
+
## Step 1: 探索项目上下文
|
|
55
55
|
|
|
56
56
|
**在提问之前，先了解当前项目状态：**
|
|
57
57
|
|
|
@@ -72,7 +72,7 @@ ls docs/ 2>/dev/null
|
|
|
72
72
|
- 了解技术栈、项目结构、最近变更
|
|
73
73
|
- 如果用户引用了文件（如 `docs/task.md`），读取该文件
|
|
74
74
|
|
|
75
|
-
##
|
|
75
|
+
## Step 2: 评估范围与领域检测
|
|
76
76
|
|
|
77
77
|
**2.1 评估范围**
|
|
78
78
|
|
|
@@ -101,7 +101,7 @@ AskUserQuestion: `header: "领域调研"`, `multiSelect: false`
|
|
|
101
101
|
|
|
102
102
|
用户选择「先调研」后，调用 `Skill: skill = "om:research", args = "任务描述"`。研究完成后，研究结论会作为头脑风暴的输入上下文。
|
|
103
103
|
|
|
104
|
-
##
|
|
104
|
+
## Step 3: 逐一澄清需求
|
|
105
105
|
|
|
106
106
|
**核心原则：一次只问一个问题。每条消息只有一个问题。**
|
|
107
107
|
|
|
@@ -155,7 +155,7 @@ AskUserQuestion: `header: "MVP"`, `multiSelect: false`
|
|
|
155
155
|
- **YAGNI** — 主动建议去掉不必要的功能
|
|
156
156
|
- **深入追问** — 如果用户选"其他"，用开放式问题跟进
|
|
157
157
|
|
|
158
|
-
##
|
|
158
|
+
## Step 4: 提出 2-3 种方案
|
|
159
159
|
|
|
160
160
|
理解需求后，**先在界面输出方案详情**（不放在 AskUserQuestion 里），再让用户选择。
|
|
161
161
|
|
|
@@ -192,7 +192,7 @@ AskUserQuestion: `header: "技术方案"`, `multiSelect: false`
|
|
|
192
192
|
| 方案 B | 单体架构 |
|
|
193
193
|
| 方案 C | 微服务架构 |
|
|
194
194
|
|
|
195
|
-
##
|
|
195
|
+
## Step 5: 分步展示设计
|
|
196
196
|
|
|
197
197
|
**逐节展示设计方案，每节确认一次：**
|
|
198
198
|
|
|
@@ -229,7 +229,7 @@ AskUserQuestion: `header: "确认"`, `multiSelect: false`
|
|
|
229
229
|
| 继续 | 设计合理，继续下一部分 |
|
|
230
230
|
| 修改 | 我有调整建议 |
|
|
231
231
|
|
|
232
|
-
##
|
|
232
|
+
## Step 6: 总结确认 + 自动路由判断
|
|
233
233
|
|
|
234
234
|
所有设计部分确认后，**先在界面展示完整总结和路由判断**，再让用户确认：
|
|
235
235
|
|
|
@@ -280,7 +280,7 @@ AskUserQuestion: `header: "下一步"`, `multiSelect: false`
|
|
|
280
280
|
| 继续探索 | 还有问题需要进一步讨论 |
|
|
281
281
|
| 仅生成文档 | 生成设计文档但不执行 |
|
|
282
282
|
|
|
283
|
-
##
|
|
283
|
+
## Step 7: 输出设计文档
|
|
284
284
|
|
|
285
285
|
总结确认后，将设计写入文档，便于后续执行时参考：
|
|
286
286
|
|
|
@@ -340,7 +340,7 @@ AskUserQuestion: `header: "下一步"`, `multiSelect: false`
|
|
|
340
340
|
| 开始执行 (推荐) | 调用 /om:plan 生成技术方案后执行 |
|
|
341
341
|
| 修改设计 | 需要调整设计方案 |
|
|
342
342
|
|
|
343
|
-
##
|
|
343
|
+
## Step 8: 路由到 plan 或直接执行
|
|
344
344
|
|
|
345
345
|
用户选择"确认并执行"后，根据路由判断结果进入不同流程：
|
|
346
346
|
|
|
@@ -358,15 +358,22 @@ openmatrix start --init-only
|
|
|
358
358
|
|
|
359
359
|
3. **写入 feature-session.json 并直接调用 feature：**
|
|
360
360
|
|
|
361
|
-
写入 `.openmatrix/feature-session.json
|
|
361
|
+
写入 `.openmatrix/feature-session.json`（与 `/om:feature` Step 0 结构一致）：
|
|
362
362
|
```json
|
|
363
363
|
{
|
|
364
|
-
"
|
|
365
|
-
"
|
|
366
|
-
"
|
|
364
|
+
"sessionId": "FEATURE-YYYYMMDDHHMMSS",
|
|
365
|
+
"status": "running",
|
|
366
|
+
"tasks": [],
|
|
367
|
+
"currentTaskIndex": 0,
|
|
368
|
+
"quality": null,
|
|
369
|
+
"failureCount": {},
|
|
370
|
+
"taskDescription": "任务描述（从头脑风暴提取）",
|
|
371
|
+
"designNotes": "关键设计要点（从 Step 5 提取）"
|
|
367
372
|
}
|
|
368
373
|
```
|
|
369
374
|
|
|
375
|
+
> **注意**: sessionId 使用当前时间戳生成，如 `FEATURE-20260522133000`。
|
|
376
|
+
|
|
370
377
|
4. **调用 Skill：**
|
|
371
378
|
```
|
|
372
379
|
Skill 工具: skill = "om:feature"
|