1343 lines
66 KiB
JSON
1343 lines
66 KiB
JSON
{
|
||
"scenarios": {
|
||
"test_engineer": [
|
||
{
|
||
"scenarioName": "自然语言查询测试任务与数据",
|
||
"description": "用户通过自然语言查询测试任务、工具、模型、机器、报告等信息，经需求解析后，由测试任务查询智能体检索并返回结构化结果。",
|
||
"userInputExamples": [
|
||
"我最近一个月开发的工具有哪些？",
|
||
"MPFAI对应功能测试Case包含哪些模型？列表展示",
|
||
"Legion 5P AMD Y570P GN20E-SIT-SKU4-1这个机台目前借用人是谁?",
|
||
"导出最近一周 zhiwen.wu 账户下所有测试任务的执行详情",
|
||
"任务TT20251021000018里BuildIssExefile_Web版本是多少？是当前最新的版本嘛？"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"requirement_parser_agent",
|
||
"test_task_query_agent",
|
||
"personal_assistant"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务路由与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为自然语言查询测试任务与数据，选择 Task Plan、需求解析Agent、测试任务查询Agent"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」（如时间范围、对象名称）"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务路由与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户查询参数，评估查询可行性"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将查询任务下发给需求解析Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "需求解析",
|
||
"agent": "requirement_parser_agent",
|
||
"agentName": "Requirement Parser Agent",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "调用 natural-language-understanding：解析用户指令中的任务意图、测试类型、关键参数与约束条件"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "调用 domain-terminology-mapping：将测试领域专业术语映射为平台统一体系"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "调用 contextual-linking：关联用户历史会话记录，延续配置偏好与任务上下文"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "将结构化查询参数返回给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "查询执行",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收需求解析Agent返回的结构化查询参数"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "将查询参数下发给测试任务查询Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 5,
|
||
"phase": "查询执行",
|
||
"agent": "test_task_query_agent",
|
||
"agentName": "Test Task Query Agent",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "调用 natural-language-query-parsing：根据用户自然语言查询，跨平台检索Tool、Model、测试报告、机器信息/状态、任务信息/状态、用户信息等全维度数据"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "将检索结果（结构化数据）返回给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 6,
|
||
"phase": "结果汇总",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收测试任务查询Agent返回的检索结果"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "对结果进行结构化整理和总结"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "移交汇总结果给 Personal Assistant"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 7,
|
||
"phase": "报告与交付",
|
||
"agent": "personal_assistant",
|
||
"agentName": "Personal Assistant",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Task Plan 汇总结果"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "生成 Markdown 格式查询报告（表格或列表形式）"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "向用户展示查询结果，提供导出功能"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "将执行结果反馈给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 8,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Personal Assistant 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "问题诊断与模型配置推荐",
|
||
"description": "用户描述测试中遇到的特定问题（如S4 WLAN YB issue），需求解析后由模型匹配与编排Agent推荐适用的测试模型及配置方案。",
|
||
"userInputExamples": [
|
||
"我目前遇到一个S4 WLAN YB的issue,需要复制该问题，但是该测试可能会先遇到Lenovo USB Ethernet Dongle先lost的问题，为此我需要用什么模型测试，需要怎么配置该模型？"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"requirement_parser_agent",
|
||
"model_matching_orchestrator_agent",
|
||
"personal_assistant"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务路由与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为问题诊断与模型配置推荐，选择 Task Plan、需求解析Agent、模型匹配与编排Agent"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」（如复现步骤、环境信息）"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务路由与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户问题，评估诊断可行性"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将任务下发给需求解析Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "需求解析",
|
||
"agent": "requirement_parser_agent",
|
||
"agentName": "Requirement Parser Agent",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "调用 natural-language-understanding：解析用户描述的issue类型、测试场景、预期行为"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "调用 domain-terminology-mapping：将issue中的专业术语映射为平台标准问题分类"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "调用 contextual-linking：关联用户历史类似问题处理记录"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "输出结构化问题描述（包含约束条件和期望输出）返回给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "模型匹配与编排",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收需求解析Agent输出的结构化问题描述"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "将问题特征作为输入下发给模型匹配与编排Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 5,
|
||
"phase": "模型匹配与编排",
|
||
"agent": "model_matching_orchestrator_agent",
|
||
"agentName": "Model Matching Orchestrator Agent",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "调用 atomic-model-retrieval：基于任务类型与功能描述，从原子模型库中召回相关模型"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "调用 model-ranking：按匹配度、执行成功率、资源消耗等指标排序，推荐最优模型组合"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "调用 intelligent-parameter-config：依据任务需求自动填充模型参数"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "调用 config-file-association：匹配模型对应的配置文件，建立模型与文件的精准映射关系"
|
||
},
|
||
{
|
||
"order": 5,
|
||
"description": "输出推荐模型列表、配置参数及配置文件路径，返回给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 6,
|
||
"phase": "结果汇总",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收模型匹配与编排Agent返回的推荐方案"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "对推荐方案进行整理和说明"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "移交汇总结果给 Personal Assistant"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 7,
|
||
"phase": "报告与交付",
|
||
"agent": "personal_assistant",
|
||
"agentName": "Personal Assistant",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Task Plan 汇总结果"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "生成 Markdown 格式推荐报告（包含推荐模型、配置参数、使用说明）"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "向用户展示推荐方案，并提供一键应用配置的能力"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "将执行结果反馈给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 8,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Personal Assistant 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "创建定时测试任务或下发模型执行",
|
||
"description": "用户要求创建定时测试任务或按照模板下发模型执行（如webrelease），经需求解析、模型匹配与编排后，由vlab任务执行Agent完成实际任务下发与调度。",
|
||
"userInputExamples": [
|
||
"帮我创建今天下午15:30执行的定时测试任务，任务为运行 MS、S4、WB、FB 四项各300圈，其他参数默认。测试机器是五码为 NS750,并且挂在 zhiwen.wu 账户下的所有机器",
|
||
"我要做webrealese，案子是Legion 5 15IRX10，请按照我之前的发起webrelease成功的模板下发模型"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"requirement_parser_agent",
|
||
"model_matching_orchestrator_agent",
|
||
"vlab_task_executor_agent",
|
||
"personal_assistant"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务路由与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为创建定时测试任务或下发模型执行，选择 Task Plan、需求解析Agent、模型匹配与编排Agent、vlab任务执行Agent"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」（如时间、机器、参数等）"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务路由与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户任务参数，评估资源可用性"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将任务下发给需求解析Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "需求解析",
|
||
"agent": "requirement_parser_agent",
|
||
"agentName": "Requirement Parser Agent",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "调用 natural-language-understanding：解析用户指令中的任务类型（测试/发布）、时间约束、测试项、机器条件等"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "调用 domain-terminology-mapping：将用户描述中的测试项（如MS、S4、WB、FB）映射为标准任务模板"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "调用 contextual-linking：关联用户历史任务模板（如webrelease成功案例）"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "输出结构化任务描述（含所有参数），返回给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "模型匹配与编排",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收需求解析Agent输出的结构化任务描述"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "将任务需求下发给模型匹配与编排Agent，获取具体的执行模型和配置"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 5,
|
||
"phase": "模型匹配与编排",
|
||
"agent": "model_matching_orchestrator_agent",
|
||
"agentName": "Model Matching Orchestrator Agent",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "调用 atomic-model-retrieval：根据任务类型召回对应的测试模型或发布模型"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "调用 model-ranking：按历史成功率、资源消耗等推荐最优模型组合"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "调用 intelligent-parameter-config：自动填充任务参数（圈数、时间、机器筛选条件）"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "调用 config-file-association：匹配模型对应的配置文件或模板"
|
||
},
|
||
{
|
||
"order": 5,
|
||
"description": "输出可执行的模型组合及完整参数配置，返回给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 6,
|
||
"phase": "任务执行调度",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收模型匹配与编排Agent返回的可执行方案"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "将方案及参数下发给vlab任务执行Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 7,
|
||
"phase": "任务执行调度",
|
||
"agent": "vlab_task_executor_agent",
|
||
"agentName": "Vlab Task Executor Agent",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "调用 yaml-parse：解析YAML格式的编排文件，获取待执行工具列表及顺序"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "调用 unit-change：根据当前登录用户名及任务需求，选择可执行机器列表，若多机则返回列表供人工选择"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "调用 task-metadata-completion：完善任务项目信息、功能域信息、任务名称，并让用户确认和支持修改"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "调用 task-status-monitor：实时监测测试机任务执行状态，判断资源占用情况，新任务智能排队，空闲时自动调度执行"
|
||
},
|
||
{
|
||
"order": 5,
|
||
"description": "调用 multi-client-communication：连接测试机客户端，传输任务数据，确保投递成功"
|
||
},
|
||
{
|
||
"order": 6,
|
||
"description": "将任务投递结果（任务ID、状态、详情页地址）返回给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 8,
|
||
"phase": "结果汇总",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收vlab任务执行Agent返回的任务执行结果"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "对执行结果进行整理和总结（任务ID、状态、链接）"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "移交汇总结果给 Personal Assistant"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 9,
|
||
"phase": "报告与交付",
|
||
"agent": "personal_assistant",
|
||
"agentName": "Personal Assistant",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Task Plan 汇总结果"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "生成 Markdown 格式任务报告（任务ID、执行状态、详情页链接、预计完成时间）"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "向用户展示任务创建成功信息，并提供任务跟踪链接"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "可选：发送邮件通知用户任务已创建/开始执行"
|
||
},
|
||
{
|
||
"order": 5,
|
||
"description": "将执行结果反馈给 Task Plan"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 10,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Personal Assistant 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
],
|
||
"debugger": [
|
||
{
|
||
"scenarioName": "Driver驱动相关知识问答",
|
||
"description": "针对与驱动程序相关的问题提供解答，涵盖驱动模型、开发规范、调试方法、常见问题排查与解决方案等知识领域",
|
||
"userInputExamples": [
|
||
"WDF驱动模型和WDM驱动模型的主要区别是什么？",
|
||
"Windows 11上如何为自制硬件编写和安装驱动程序？",
|
||
"遇到驱动程序代码0xC0000001蓝屏错误，可能的原因有哪些？",
|
||
"如何调试一个导致系统启动时卡死的驱动程序？",
|
||
"请教一下驱动程序签名的最新要求和流程"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"Knowledge Q&A"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务路由与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为知识问答，选择 Task Plan、Knowledge Q&A"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务路由与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "分析需求，评估可行性，输出待补充信息清单"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将结构化任务指令下发给Knowledge Q&A"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "执行与工具调用",
|
||
"agent": "Knowledge Q&A",
|
||
"agentName": "Knowledge Q&A",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Testing and Debugging Q&A",
|
||
"description": "提供笔记本电脑测试和调试的知识问答服务，通过用户提供的简单自然语言描述，服务可快速定位相关知识文档，提供清晰的排查步骤与修复方案等相关知识内容。"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Knowledge Q&A 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "OS Feature解析",
|
||
"description": "解析用户输入的操作系统功能名称或描述，提供其技术细节、实现原理、适用场景、配置方法及与其他功能的关联性说明",
|
||
"userInputExamples": [
|
||
"请解释一下 Windows 的 VBS (Virtualization-based Security) 功能",
|
||
"什么是 Control Flow Guard (CFG) 及其工作原理？",
|
||
"帮我解析一下 Linux 内核的 cgroups v2 的功能特性",
|
||
"Hyper-V 的嵌套虚拟化需要什么硬件支持和配置？",
|
||
"macOS 的 SIP (System Integrity Protection) 是如何工作的？"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"Knowledge Q&A"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务路由与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为知识问答，选择 Task Plan、Knowledge Q&A"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务路由与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "分析需求，评估可行性，输出待补充信息清单"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将结构化任务指令下发给Knowledge Q&A"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "执行与工具调用",
|
||
"agent": "Knowledge Q&A",
|
||
"agentName": "Knowledge Q&A",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Testing and Debugging Q&A",
|
||
"description": "提供笔记本电脑测试和调试的知识问答服务，通过用户提供的简单自然语言描述，服务可快速定位相关知识文档，提供清晰的排查步骤与修复方案等相关知识内容。"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Knowledge Q&A 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "WHQL Case 对应Spec提取",
|
||
"description": "根据提供的 WHQL (Windows Hardware Quality Labs) 测试用例编号或名称，自动定位并提取其对应的测试规范文档、技术要求、通过标准及关联的硬件兼容性列表",
|
||
"userInputExamples": [
|
||
"提取测试用例 DEVICE.FUNDAMENTAL.RELIABILITY 对应的详细规范",
|
||
"帮我找一下 USBXHCI.SYS 这个 WHQL Case 相关的 Spec 要求",
|
||
"查看 DXVAHD (DXVA High Definition) 相关 WHQL 测试的规格说明",
|
||
"需要 HIDClass 驱动测试用例 DEVX.MOUSE.TEST 的认证标准",
|
||
"获取与 ACPI 电源管理测试相关的所有 Case 和其规格链接"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"Knowledge Q&A"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务路由与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为知识问答，选择 Task Plan、Knowledge Q&A"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务路由与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "分析需求，评估可行性，输出待补充信息清单"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将结构化任务指令下发给Knowledge Q&A"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "执行与工具调用",
|
||
"agent": "Knowledge Q&A",
|
||
"agentName": "Knowledge Q&A",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Testing and Debugging Q&A",
|
||
"description": "提供笔记本电脑测试和调试的知识问答服务，通过用户提供的简单自然语言描述，服务可快速定位相关知识文档，提供清晰的排查步骤与修复方案等相关知识内容。"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Knowledge Q&A 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "项目信息问答",
|
||
"description": "回答关于特定项目的基础信息，包括项目Phase、项目PM、项目PPM、项目BIOS Code、文档清单、项目文档链接等",
|
||
"userInputExamples": [
|
||
"项目 Phoenix 的PPM是谁？",
|
||
"Project_A 的 OD文件下载地址是什么？",
|
||
"我想了解项目代号‘昆仑’的详细资料和当前所处Phase",
|
||
"Project_Beta 的EVT时间是什么时候？",
|
||
"查询项目 Thunder 的SW Plan文档"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"Project Query"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务解析与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为项目信息问答，选择 Task Plan、Project Query"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务解析与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "分析需求，评估可行性，输出待补充信息清单"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将结构化任务指令下发给Project Query"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "查询项目基础信息",
|
||
"agent": "Project Query",
|
||
"agentName": "Project Query",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Project Query",
|
||
"description": "基于用户输入的项目名称、别名和五码信息，查询项目的基础信息，包含项目名称、项目别名、BU、PPM、BIOS Code、PJE、Phase"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "查询项目文档信息",
|
||
"agent": "Project Query",
|
||
"agentName": "Project Query",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Project Query",
|
||
"description": "基于用户输入的项目名称、别名、五码和文档名称信息，查询该项目的指定文档，并理解文档内的相关内容"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 5,
|
||
"phase": "结果汇总",
|
||
"agent": "Project Query",
|
||
"agentName": "Project Query",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "合并项目基础信息和项目文档信息，进行总结输出"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 6,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Project Query 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "针对问题自动推荐Debug工具或者批处理脚本，支持下载",
|
||
"description": "根据用户描述的系统或软件问题现象，自动分析并推荐适用的调试工具、诊断脚本或批处理命令，并提供工具/脚本的获取链接或直接生成简易脚本供下载",
|
||
"userInputExamples": [
|
||
"我的程序内存泄漏了，推荐一个分析工具并告诉我怎么用,然后帮我下载",
|
||
"系统频繁蓝屏，错误代码是 0x133，有什么调试脚本可以帮我收集信息？",
|
||
"网络连接时断时续，请推荐一个诊断批处理脚本，生成下载链接",
|
||
"怀疑是注册表损坏导致服务无法启动，有什么工具可以检查，提供下载链接？",
|
||
"帮我生成一个能一键收集系统日志和进程列表的 PowerShell 脚本"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"Knowledge Q&A",
|
||
"Data Download"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务路由与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为知识问答和数据下载，选择 Task Plan、Knowledge Q&A、Data Download"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务路由与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "分析需求，评估可行性，输出待补充信息清单"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将结构化任务指令下发给Knowledge Q&A"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "执行与工具调用",
|
||
"agent": "Knowledge Q&A",
|
||
"agentName": "Knowledge Q&A",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Testing and Debugging Q&A",
|
||
"description": "提供笔记本电脑测试和调试的知识问答服务，通过用户提供的简单自然语言描述，服务可快速定位相关知识文档，提供清晰的排查步骤与修复方案等相关知识内容。"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "连接互联网查询相关脚本或工具信息，将生成的脚本或获取到的工具信息发送给 Data Download"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "执行与工具调用",
|
||
"agent": "Data Download",
|
||
"agentName": "Data Download",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Data Download",
|
||
"description": "将指定的数据或文档打包生成下载链接"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 5,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Knowledge Q&A、Data Download 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "根据请求自动输出项目Issue汇总报告",
|
||
"description": "接收项目名称、时间范围、状态等筛选条件，自动从 Issue 管理系统中汇总数据，生成包含 Issue 数量、状态分布、处理人分布、趋势分析等信息的结构化报告",
|
||
"userInputExamples": [
|
||
"生成项目 CoreLib 所有 Issue 汇总报告",
|
||
"请输出项目 Phoenix 当前所有‘Open’状态的 Issue 列表和统计",
|
||
"我需要一个关于项目 Thunder 最近一个月SW的issue的分析报告",
|
||
"汇总项目‘昆仑’的 Issue 处理情况",
|
||
"生成一份按模块（Component）分类的项目 Alpha 的 Issue 统计报告"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"Issue Query"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务解析与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为issue数据报告汇总，选择 Task Plan、Issue Query"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务解析与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "分析需求，评估可行性，输出待补充信息清单"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将结构化任务指令下发给Issue Query"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "执行与工具调用",
|
||
"agent": "Issue Query",
|
||
"agentName": "Issue Query",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"scenarioName": "Issue Query",
|
||
"description": "通过输入Issue描述或defect ID，提供TDMS系统中Issue的数据查询服务，支持查询的Issue数据包含Issue基础信息（包含Issue的标题、描述、所属项目、状态、解决方案），通过输入项目名称或五码信息，查询项目Issue统计数据（包含指定项目下Issue的总数量、Open Issue数量、Close Issue数量、Close Rate数据）"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "将查询的数据进行汇总分析，生成对应的数据报告"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Knowledge Q&A、Data Download 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有子任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"scenarioName": "根据Issue描述或DefectID查询呈现相关Issue的信息和log解析报告",
|
||
"description": "根据用户提供的 Issue 描述关键词或具体的缺陷 ID，从数据库中查询并呈现该 Issue 的详细信息（如标题、状态、处理人、创建/关闭时间），并自动解析、摘要相关的日志附件，形成关键时间线、错误信息和潜在原因的分析摘要",
|
||
"userInputExamples": [
|
||
"查询缺陷 ID BUG-2024-1024 的详细信息，并分析它的日志",
|
||
"搜索所有描述中包含‘内存越界访问’的 Issue 并展示最新的一条",
|
||
"请查找并分析最近一周内与‘USB 枚举失败’相关的所有 Issue 和日志",
|
||
"根据 Defect ID 12345 获取完整的处理记录和日志解析摘要",
|
||
"帮我查找标题里有‘系统启动卡住’的 Issue，并看看日志里有什么线索"
|
||
],
|
||
"participants": [
|
||
"super_agent",
|
||
"task_plan",
|
||
"Issue Query",
|
||
"Log Query",
|
||
"Debugging Strategy Analysis"
|
||
],
|
||
"flow": [
|
||
{
|
||
"step": 1,
|
||
"phase": "任务解析与规划",
|
||
"agent": "super_agent",
|
||
"agentName": "Super Master",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "解析用户目标、范围、输入/输出与硬约束"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "识别意图为issue分析，选择 Task Plan、Issue Query、Log Query、Debugging Strategy Analysis"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "对信息不足处提出「最少必要问题」"
|
||
},
|
||
{
|
||
"order": 4,
|
||
"description": "移交执行权限给 Task Plan Agent"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 2,
|
||
"phase": "任务解析与规划",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "分析需求，评估可行性，输出待补充信息清单"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "输出任务拆分、依赖、分工、里程碑与交付物"
|
||
},
|
||
{
|
||
"order": 3,
|
||
"description": "将结构化任务指令下发给Issue Query、Log Query、Debugging Strategy Analysis"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 3,
|
||
"phase": "相似issue查询",
|
||
"agent": "Issue Query",
|
||
"agentName": "Issue Query",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "基于用户输入的issue描述或issue defect ID，查询相似的Issue信息，包含Issue的标题、描述、所属项目、状态、解决方案"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 4,
|
||
"phase": "issue相关log解析结果查询",
|
||
"agent": "Log Query",
|
||
"agentName": "Log Query",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "基于用户输入的issue defect ID，查询对应的log解析结果文档内容，并将内容汇总后输出对应结论"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 5,
|
||
"phase": "issue调试策略查询",
|
||
"agent": "Debugging Strategy Analysis",
|
||
"agentName": "Debugging Strategy Analysis",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "基于用户输入的Issue描述，对接DIKW系统获取对应Issue的调试策略"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 6,
|
||
"phase": "任务结果反馈",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 Issue Query、Log Query、Debugging Strategy Analysis 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "汇总反馈内容，总结输出结论"
|
||
}
|
||
]
|
||
},
|
||
{
|
||
"step": 7,
|
||
"phase": "任务闭环",
|
||
"agent": "task_plan",
|
||
"agentName": "Task Plan",
|
||
"scenarioSteps": [
|
||
{
|
||
"order": 1,
|
||
"description": "接收 task_plan 的反馈"
|
||
},
|
||
{
|
||
"order": 2,
|
||
"description": "确认所有任务已完成，更新任务状态为已完成"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
} |