intention-coding 0.3.8 → 0.4.1
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/package.json +1 -1
- package/dist/db/file-storage.js +0 -638
- package/dist/index.js +0 -26
- package/dist/server/index.js +0 -88
- package/dist/services/bug-fix-agent/index.js +0 -320
- package/dist/services/change-summarizer/index.js +0 -123
- package/dist/services/change-summarizer/prompt/change-analysis.js +0 -56
- package/dist/services/code-generator/index.js +0 -403
- package/dist/services/code-generator/stages/execution-stage.js +0 -549
- package/dist/services/code-generator/stages/ideation-stage.js +0 -267
- package/dist/services/code-generator/stages/optimization-stage.js +0 -334
- package/dist/services/code-generator/stages/planning-stage.js +0 -295
- package/dist/services/code-generator/stages/research-stage.js +0 -283
- package/dist/services/code-generator/stages/review-stage.js +0 -270
- package/dist/services/code-generator/types.js +0 -37
- package/dist/services/code-generator/utils/instruction-executor.js +0 -207
- package/dist/services/code-generator/workflow-manager.js +0 -252
- package/dist/services/image-analysis/analyzer.js +0 -530
- package/dist/services/image-analysis/index.js +0 -406
- package/dist/services/image-analysis/types.js +0 -46
- package/dist/services/image-converter/converter.js +0 -310
- package/dist/services/image-converter/index.js +0 -262
- package/dist/services/image-converter/types.js +0 -31
- package/dist/services/integrated-generator/index.js +0 -1297
- package/dist/services/pdf2md/index.js +0 -180
- package/dist/services/project-template/index.js +0 -83
- package/dist/services/project-template/prompt/project-rules.js +0 -98
- package/dist/services/requirement-analyzer/chunk-reader.js +0 -218
- package/dist/services/requirement-analyzer/core/document-generator.js +0 -254
- package/dist/services/requirement-analyzer/core/intelligent-analyzer.js +0 -169
- package/dist/services/requirement-analyzer/core/project-analyzer.js +0 -199
- package/dist/services/requirement-analyzer/core/requirement-analyzer-service.js +0 -191
- package/dist/services/requirement-analyzer/core/template-selector.js +0 -124
- package/dist/services/requirement-analyzer/core/types.js +0 -23
- package/dist/services/requirement-analyzer/index.js +0 -177
- package/dist/services/requirement-analyzer/prompt/api-template.js +0 -302
- package/dist/services/requirement-analyzer/prompt/app-template.js +0 -455
- package/dist/services/requirement-analyzer/prompt/intelligent-requirement-analysis.js +0 -92
- package/dist/services/requirement-analyzer/prompt/pc-page-template.js +0 -582
- package/dist/services/requirement-analyzer/prompt/requirement-analysis.js +0 -664
- package/dist/services/requirement-analyzer/prompt/sdk-template.js +0 -582
- package/dist/services/requirement-analyzer/utils/file-reader.js +0 -169
- package/dist/services/world2md/index.js +0 -157
- package/dist/types/index.js +0 -2
- package/dist/utils/common.js +0 -72
- package/dist/utils/config.js +0 -163
- package/dist/utils/context-manager.js +0 -114
- package/dist/utils/dify.js +0 -243
- package/dist/utils/logger.js +0 -129
- package/dist/utils/openai.js +0 -225
- package/dist/utils/pack.js +0 -75
|
@@ -1,403 +0,0 @@
|
|
|
1
|
-
"use strict";
|
|
2
|
-
/**
|
|
3
|
-
* 六步工作流程代码生成工具
|
|
4
|
-
* 按照 workflow.md 中定义的流程指导用户完成代码开发
|
|
5
|
-
*/
|
|
6
|
-
var __awaiter = (this && this.__awaiter) || function (thisArg, _arguments, P, generator) {
|
|
7
|
-
function adopt(value) { return value instanceof P ? value : new P(function (resolve) { resolve(value); }); }
|
|
8
|
-
return new (P || (P = Promise))(function (resolve, reject) {
|
|
9
|
-
function fulfilled(value) { try { step(generator.next(value)); } catch (e) { reject(e); } }
|
|
10
|
-
function rejected(value) { try { step(generator["throw"](value)); } catch (e) { reject(e); } }
|
|
11
|
-
function step(result) { result.done ? resolve(result.value) : adopt(result.value).then(fulfilled, rejected); }
|
|
12
|
-
step((generator = generator.apply(thisArg, _arguments || [])).next());
|
|
13
|
-
});
|
|
14
|
-
};
|
|
15
|
-
Object.defineProperty(exports, "__esModule", { value: true });
|
|
16
|
-
exports.codeGeneratorTool = void 0;
|
|
17
|
-
const zod_1 = require("zod");
|
|
18
|
-
const logger_1 = require("../../utils/logger");
|
|
19
|
-
// 六步工作流程阶段定义
|
|
20
|
-
var WorkflowStage;
|
|
21
|
-
(function (WorkflowStage) {
|
|
22
|
-
WorkflowStage["RESEARCH"] = "research";
|
|
23
|
-
WorkflowStage["IDEATION"] = "ideation";
|
|
24
|
-
WorkflowStage["PLANNING"] = "planning";
|
|
25
|
-
WorkflowStage["EXECUTION"] = "execution";
|
|
26
|
-
WorkflowStage["OPTIMIZATION"] = "optimization";
|
|
27
|
-
WorkflowStage["REVIEW"] = "review"; // 评审
|
|
28
|
-
})(WorkflowStage || (WorkflowStage = {}));
|
|
29
|
-
// 参数验证Schema
|
|
30
|
-
const CodeGeneratorParamsSchema = zod_1.z.object({
|
|
31
|
-
task_description: zod_1.z.string().describe("要开发的任务描述"),
|
|
32
|
-
current_stage: zod_1.z.enum([
|
|
33
|
-
"research", "ideation", "planning", "execution", "optimization", "review"
|
|
34
|
-
]).optional().default("research").describe("当前工作流程阶段"),
|
|
35
|
-
user_input: zod_1.z.any().optional().describe("用户在当前阶段的输入数据"),
|
|
36
|
-
project_path: zod_1.z.string().optional().describe("项目路径"),
|
|
37
|
-
});
|
|
38
|
-
/**
|
|
39
|
-
* 获取阶段模式标签
|
|
40
|
-
*/
|
|
41
|
-
function getStageMode(stage) {
|
|
42
|
-
switch (stage) {
|
|
43
|
-
case WorkflowStage.RESEARCH:
|
|
44
|
-
return '[模式:研究]';
|
|
45
|
-
case WorkflowStage.IDEATION:
|
|
46
|
-
return '[模式:构思]';
|
|
47
|
-
case WorkflowStage.PLANNING:
|
|
48
|
-
return '[模式:计划]';
|
|
49
|
-
case WorkflowStage.EXECUTION:
|
|
50
|
-
return '[模式:执行]';
|
|
51
|
-
case WorkflowStage.OPTIMIZATION:
|
|
52
|
-
return '[模式:优化]';
|
|
53
|
-
case WorkflowStage.REVIEW:
|
|
54
|
-
return '[模式:评审]';
|
|
55
|
-
default:
|
|
56
|
-
return '[模式:未知]';
|
|
57
|
-
}
|
|
58
|
-
}
|
|
59
|
-
/**
|
|
60
|
-
* 生成研究阶段指导
|
|
61
|
-
*/
|
|
62
|
-
function generateResearchGuidance(taskDescription) {
|
|
63
|
-
return __awaiter(this, void 0, void 0, function* () {
|
|
64
|
-
const mode = getStageMode(WorkflowStage.RESEARCH);
|
|
65
|
-
return `${mode} - 需求分析和完整性评估
|
|
66
|
-
|
|
67
|
-
## 任务描述
|
|
68
|
-
${taskDescription}
|
|
69
|
-
|
|
70
|
-
## 执行步骤
|
|
71
|
-
|
|
72
|
-
### 1. 需求完整性分析(0-10分评分)
|
|
73
|
-
请按照以下维度对任务需求进行评分:
|
|
74
|
-
|
|
75
|
-
**目标明确性(0-3分)**
|
|
76
|
-
- 3分:目标非常清晰,明确要解决的问题和实现的功能
|
|
77
|
-
- 2分:目标基本清晰,但有些细节需要澄清
|
|
78
|
-
- 1分:目标模糊,需要大量澄清
|
|
79
|
-
- 0分:目标完全不明确
|
|
80
|
-
|
|
81
|
-
**预期结果(0-3分)**
|
|
82
|
-
- 3分:成功标准和交付物非常明确
|
|
83
|
-
- 2分:有基本的成功标准,但不够详细
|
|
84
|
-
- 1分:成功标准模糊
|
|
85
|
-
- 0分:没有明确的成功标准
|
|
86
|
-
|
|
87
|
-
**边界范围(0-2分)**
|
|
88
|
-
- 2分:任务范围和边界非常清楚
|
|
89
|
-
- 1分:范围基本明确,但边界模糊
|
|
90
|
-
- 0分:范围和边界都不清楚
|
|
91
|
-
|
|
92
|
-
**约束条件(0-2分)**
|
|
93
|
-
- 2分:时间、性能、业务限制等都有说明
|
|
94
|
-
- 1分:有部分约束说明
|
|
95
|
-
- 0分:没有约束条件说明
|
|
96
|
-
|
|
97
|
-
### 2. 项目技术环境分析
|
|
98
|
-
- 检查项目根目录的 CLAUDE.md 文件
|
|
99
|
-
- 分析 package.json、requirements.txt 等配置文件
|
|
100
|
-
- 识别技术栈和框架版本
|
|
101
|
-
- 获取项目结构信息
|
|
102
|
-
|
|
103
|
-
### 3. 完整性评估
|
|
104
|
-
- 计算总体完整性得分(总分10分)
|
|
105
|
-
- 如果得分 >= 7分:准备进入构思阶段
|
|
106
|
-
- 如果得分 < 7分:列出需要补充的关键信息
|
|
107
|
-
|
|
108
|
-
## 预期输出
|
|
109
|
-
需求完整性评分报告,包含各维度得分和总分。如果评分低于7分,请列出具体的补充问题。
|
|
110
|
-
|
|
111
|
-
## 下一步
|
|
112
|
-
完成需求分析后,请使用 current_stage="ideation" 进入构思阶段。`;
|
|
113
|
-
});
|
|
114
|
-
}
|
|
115
|
-
/**
|
|
116
|
-
* 生成构思阶段指导
|
|
117
|
-
*/
|
|
118
|
-
function generateIdeationGuidance(taskDescription, userInput) {
|
|
119
|
-
return __awaiter(this, void 0, void 0, function* () {
|
|
120
|
-
const mode = getStageMode(WorkflowStage.IDEATION);
|
|
121
|
-
return `${mode} - 解决方案设计
|
|
122
|
-
|
|
123
|
-
## 任务需求
|
|
124
|
-
${taskDescription}
|
|
125
|
-
|
|
126
|
-
## 执行步骤
|
|
127
|
-
|
|
128
|
-
### 1. 方案生成
|
|
129
|
-
请设计至少2-3个不同的解决方案,每个方案需要包含:
|
|
130
|
-
|
|
131
|
-
**方案格式示例:**
|
|
132
|
-
**方案 1:[方案名称]**
|
|
133
|
-
- **描述**:详细说明解决思路和实现方式
|
|
134
|
-
- **优点**:
|
|
135
|
-
- 优点1
|
|
136
|
-
- 优点2
|
|
137
|
-
- **缺点**:
|
|
138
|
-
- 缺点1
|
|
139
|
-
- 缺点2
|
|
140
|
-
- **复杂度**:low/medium/high
|
|
141
|
-
- **估算时间**:具体时间估算
|
|
142
|
-
- **技术要求**:需要的技术和依赖
|
|
143
|
-
- **风险等级**:low/medium/high
|
|
144
|
-
- **适用场景**:什么情况下选择这个方案
|
|
145
|
-
|
|
146
|
-
### 2. 方案评估
|
|
147
|
-
对每个方案进行客观评估:
|
|
148
|
-
- 可行性评估(1-5分)
|
|
149
|
-
- 质量评估(1-5分)
|
|
150
|
-
- 风险评估(1-5分)
|
|
151
|
-
- 成本效益(1-5分)
|
|
152
|
-
|
|
153
|
-
### 3. 方案选择
|
|
154
|
-
选择最适合的方案,并说明选择理由。
|
|
155
|
-
|
|
156
|
-
## 预期输出
|
|
157
|
-
至少2-3个详细的解决方案,包含完整的评估信息和推荐选择。
|
|
158
|
-
|
|
159
|
-
## 下一步
|
|
160
|
-
选定方案后,请使用 current_stage="planning" 进入计划阶段。`;
|
|
161
|
-
});
|
|
162
|
-
}
|
|
163
|
-
/**
|
|
164
|
-
* 生成计划阶段指导
|
|
165
|
-
*/
|
|
166
|
-
function generatePlanningGuidance(taskDescription, userInput) {
|
|
167
|
-
return __awaiter(this, void 0, void 0, function* () {
|
|
168
|
-
const mode = getStageMode(WorkflowStage.PLANNING);
|
|
169
|
-
return `${mode} - 执行计划制定
|
|
170
|
-
|
|
171
|
-
## 任务描述
|
|
172
|
-
${taskDescription}
|
|
173
|
-
|
|
174
|
-
## 执行步骤
|
|
175
|
-
|
|
176
|
-
### 1. 方案细化
|
|
177
|
-
将选定的解决方案细化为具体的实现步骤:
|
|
178
|
-
- 技术架构分析
|
|
179
|
-
- 文件结构规划
|
|
180
|
-
- 核心实现分析
|
|
181
|
-
- 依赖和资源需求
|
|
182
|
-
|
|
183
|
-
### 2. 执行计划制定
|
|
184
|
-
创建详细的执行计划,每个步骤必须包含:
|
|
185
|
-
|
|
186
|
-
**步骤 X:[步骤名称]**
|
|
187
|
-
- **类型**:file_creation | file_modification | function_implementation | class_implementation | test_creation | configuration
|
|
188
|
-
- **描述**:详细说明要做什么
|
|
189
|
-
- **目标文件**:涉及的文件路径
|
|
190
|
-
- **原子操作**:
|
|
191
|
-
- 创建文件:具体文件路径和基本结构
|
|
192
|
-
- 实现函数:函数签名和核心逻辑概要
|
|
193
|
-
- 修改配置:具体的配置项和值
|
|
194
|
-
- **预期结果**:完成后的状态和效果
|
|
195
|
-
- **依赖步骤**:必须先完成的步骤
|
|
196
|
-
- **估算时间**:预计执行时间
|
|
197
|
-
|
|
198
|
-
### 3. 计划审核
|
|
199
|
-
检查计划的完整性和可行性:
|
|
200
|
-
- 步骤顺序是否合理
|
|
201
|
-
- 依赖关系是否正确
|
|
202
|
-
- 时间估算是否现实
|
|
203
|
-
- 是否遗漏关键步骤
|
|
204
|
-
|
|
205
|
-
## 重要提醒
|
|
206
|
-
- 在导入语句之前添加使用方法注释(关键规则)
|
|
207
|
-
- 计划将存储在项目根目录 .claude/plan/任务名.md 中
|
|
208
|
-
- 如需新库,标注需要使用 Context7 查询
|
|
209
|
-
|
|
210
|
-
## 预期输出
|
|
211
|
-
完整、详细的执行计划,包含所有原子操作步骤。
|
|
212
|
-
|
|
213
|
-
## 下一步
|
|
214
|
-
计划制定完成后,请用户批准,然后使用 current_stage="execution" 进入执行阶段。`;
|
|
215
|
-
});
|
|
216
|
-
}
|
|
217
|
-
/**
|
|
218
|
-
* 生成执行阶段指导
|
|
219
|
-
*/
|
|
220
|
-
function generateExecutionGuidance(taskDescription, userInput) {
|
|
221
|
-
return __awaiter(this, void 0, void 0, function* () {
|
|
222
|
-
const mode = getStageMode(WorkflowStage.EXECUTION);
|
|
223
|
-
return `${mode} - 代码实施
|
|
224
|
-
|
|
225
|
-
## 任务描述
|
|
226
|
-
${taskDescription}
|
|
227
|
-
|
|
228
|
-
## 执行原则
|
|
229
|
-
|
|
230
|
-
### 1. 严格按计划执行
|
|
231
|
-
- 按照步骤顺序进行,不跳过任何步骤
|
|
232
|
-
- 确保每个步骤的完整性
|
|
233
|
-
- 遵循原子操作原则
|
|
234
|
-
|
|
235
|
-
### 2. 代码质量要求
|
|
236
|
-
- 遵循项目的代码规范和最佳实践
|
|
237
|
-
- **关键规则**:在导入语句之前添加使用方法注释
|
|
238
|
-
- 保持代码的可读性和可维护性
|
|
239
|
-
- 添加必要的注释和文档
|
|
240
|
-
|
|
241
|
-
### 3. 进度管理
|
|
242
|
-
- 在关键里程碑请求用户反馈
|
|
243
|
-
- 及时报告遇到的问题
|
|
244
|
-
- 保持与计划的一致性
|
|
245
|
-
|
|
246
|
-
## 执行步骤
|
|
247
|
-
1. 创建 .claude/plan/ 目录(如果不存在)
|
|
248
|
-
2. 将执行计划保存到 .claude/plan/任务名.md
|
|
249
|
-
3. 按计划逐步实施代码
|
|
250
|
-
4. 在关键节点请求用户确认
|
|
251
|
-
|
|
252
|
-
## 预期输出
|
|
253
|
-
按计划完成的代码实施,包含所有必要的文件、函数和配置。
|
|
254
|
-
|
|
255
|
-
## 下一步
|
|
256
|
-
执行完成后,请使用 current_stage="optimization" 进入优化阶段。`;
|
|
257
|
-
});
|
|
258
|
-
}
|
|
259
|
-
/**
|
|
260
|
-
* 生成优化阶段指导
|
|
261
|
-
*/
|
|
262
|
-
function generateOptimizationGuidance(taskDescription, userInput) {
|
|
263
|
-
return __awaiter(this, void 0, void 0, function* () {
|
|
264
|
-
const mode = getStageMode(WorkflowStage.OPTIMIZATION);
|
|
265
|
-
return `${mode} - 代码质量优化
|
|
266
|
-
|
|
267
|
-
## 任务描述
|
|
268
|
-
${taskDescription}
|
|
269
|
-
|
|
270
|
-
## 执行步骤
|
|
271
|
-
|
|
272
|
-
### 1. 代码分析
|
|
273
|
-
自动分析本次任务实现的代码:
|
|
274
|
-
- 代码结构和架构设计
|
|
275
|
-
- 代码质量和规范遵循情况
|
|
276
|
-
- 潜在的性能问题
|
|
277
|
-
- 冗余、低效或垃圾代码
|
|
278
|
-
- 可维护性和可扩展性
|
|
279
|
-
|
|
280
|
-
### 2. 优化建议生成
|
|
281
|
-
为每个问题提出针对性的优化方案:
|
|
282
|
-
- 问题描述和影响范围
|
|
283
|
-
- 具体的优化方案
|
|
284
|
-
- 优化理由和预期收益
|
|
285
|
-
- 实施难度和风险评估
|
|
286
|
-
- 按优先级排序
|
|
287
|
-
|
|
288
|
-
### 3. 优化实施
|
|
289
|
-
用户确认后执行相关优化功能:
|
|
290
|
-
- 按优先级逐项实施
|
|
291
|
-
- 保持代码功能的完整性
|
|
292
|
-
- 验证优化后的代码正确性
|
|
293
|
-
- 测试优化效果
|
|
294
|
-
|
|
295
|
-
## 优化类别
|
|
296
|
-
- **性能优化**:算法优化、数据结构改进、缓存策略
|
|
297
|
-
- **代码质量优化**:重构冗余代码、改进命名和结构
|
|
298
|
-
- **架构优化**:模块解耦、接口简化、依赖优化
|
|
299
|
-
- **安全性优化**:输入验证、错误信息处理、权限控制
|
|
300
|
-
|
|
301
|
-
## 预期输出
|
|
302
|
-
优先级排序的优化建议清单和优化后的代码。
|
|
303
|
-
|
|
304
|
-
## 下一步
|
|
305
|
-
优化完成后,请使用 current_stage="review" 进入评审阶段。`;
|
|
306
|
-
});
|
|
307
|
-
}
|
|
308
|
-
/**
|
|
309
|
-
* 生成评审阶段指导
|
|
310
|
-
*/
|
|
311
|
-
function generateReviewGuidance(taskDescription, userInput) {
|
|
312
|
-
return __awaiter(this, void 0, void 0, function* () {
|
|
313
|
-
const mode = getStageMode(WorkflowStage.REVIEW);
|
|
314
|
-
return `${mode} - 最终评估
|
|
315
|
-
|
|
316
|
-
## 任务描述
|
|
317
|
-
${taskDescription}
|
|
318
|
-
|
|
319
|
-
## 执行步骤
|
|
320
|
-
|
|
321
|
-
### 1. 执行结果评估
|
|
322
|
-
全面评估任务执行结果:
|
|
323
|
-
- 功能完成度评估
|
|
324
|
-
- 技术实现评估
|
|
325
|
-
- 计划执行评估
|
|
326
|
-
- 质量保证评估
|
|
327
|
-
- 交付物检查
|
|
328
|
-
|
|
329
|
-
### 2. 计划对比分析
|
|
330
|
-
对比原始计划与实际执行情况:
|
|
331
|
-
- 步骤执行对比
|
|
332
|
-
- 时间对比分析
|
|
333
|
-
- 技术方案对比
|
|
334
|
-
- 质量标准对比
|
|
335
|
-
- 风险管理对比
|
|
336
|
-
|
|
337
|
-
### 3. 最终确认
|
|
338
|
-
提供完成总结,请求用户最终确认:
|
|
339
|
-
- 任务完成总结报告
|
|
340
|
-
- 交付物清单
|
|
341
|
-
- 质量检查结果
|
|
342
|
-
- 用户确认和反馈收集
|
|
343
|
-
|
|
344
|
-
## 评估维度
|
|
345
|
-
- [ ] 核心功能是否完全实现?
|
|
346
|
-
- [ ] 所有需求是否得到满足?
|
|
347
|
-
- [ ] 代码质量是否达标?
|
|
348
|
-
- [ ] 文档是否完整?
|
|
349
|
-
- [ ] 是否遵循最佳实践?
|
|
350
|
-
|
|
351
|
-
## 预期输出
|
|
352
|
-
详细的评估报告和任务完成确认。
|
|
353
|
-
|
|
354
|
-
## 完成
|
|
355
|
-
🎉 恭喜!六步工作流程已完成。您可以开始新的任务或对当前结果进行进一步改进。`;
|
|
356
|
-
});
|
|
357
|
-
}
|
|
358
|
-
/**
|
|
359
|
-
* 编程智能体
|
|
360
|
-
*/
|
|
361
|
-
exports.codeGeneratorTool = {
|
|
362
|
-
name: "编程智能体",
|
|
363
|
-
description: "专业AI编程助手,提供结构化六阶段开发工作流(研究→构思→计划→执行→优化→评审),按照workflow.md中定义的流程指导用户完成代码开发",
|
|
364
|
-
parameters: CodeGeneratorParamsSchema,
|
|
365
|
-
execute: (args) => __awaiter(void 0, void 0, void 0, function* () {
|
|
366
|
-
const { task_description, current_stage, user_input, project_path } = args;
|
|
367
|
-
try {
|
|
368
|
-
logger_1.logger.info("六步工作流程代码生成开始执行", {
|
|
369
|
-
current_stage,
|
|
370
|
-
task_description: task_description.substring(0, 100)
|
|
371
|
-
});
|
|
372
|
-
let guidance;
|
|
373
|
-
switch (current_stage) {
|
|
374
|
-
case WorkflowStage.RESEARCH:
|
|
375
|
-
guidance = yield generateResearchGuidance(task_description);
|
|
376
|
-
break;
|
|
377
|
-
case WorkflowStage.IDEATION:
|
|
378
|
-
guidance = yield generateIdeationGuidance(task_description, user_input);
|
|
379
|
-
break;
|
|
380
|
-
case WorkflowStage.PLANNING:
|
|
381
|
-
guidance = yield generatePlanningGuidance(task_description, user_input);
|
|
382
|
-
break;
|
|
383
|
-
case WorkflowStage.EXECUTION:
|
|
384
|
-
guidance = yield generateExecutionGuidance(task_description, user_input);
|
|
385
|
-
break;
|
|
386
|
-
case WorkflowStage.OPTIMIZATION:
|
|
387
|
-
guidance = yield generateOptimizationGuidance(task_description, user_input);
|
|
388
|
-
break;
|
|
389
|
-
case WorkflowStage.REVIEW:
|
|
390
|
-
guidance = yield generateReviewGuidance(task_description, user_input);
|
|
391
|
-
break;
|
|
392
|
-
default:
|
|
393
|
-
throw new Error(`不支持的工作流程阶段: ${current_stage}`);
|
|
394
|
-
}
|
|
395
|
-
logger_1.logger.info("六步工作流程指导生成完成", { current_stage });
|
|
396
|
-
return guidance;
|
|
397
|
-
}
|
|
398
|
-
catch (error) {
|
|
399
|
-
logger_1.logger.error("六步工作流程执行失败", { error, args });
|
|
400
|
-
return `❌ 工作流程执行失败: ${error instanceof Error ? error.message : '未知错误'}`;
|
|
401
|
-
}
|
|
402
|
-
}),
|
|
403
|
-
};
|