修复执行者把「跳过顾问」读成「跳过确认」(不改system-prompt.txt,锚点消息为执行侧唯一指令位):task_brief锚点硬指令化——Missing/待确认逐项先问用户等答复,点名「用户跳过的只是顾问阶段不是确认环节」,唯用户明说别问才可用默认且须列出待检,禁止改写为按默认执行;handoff工具描述去毒示例just do it→just move on并声明user_skip只跳顾问对话不豁免后续确认,收尾要求非ready的brief必须带Missing清单;advising提示词同步「用户跳过的是planning chat不是这些问题」。根因:执行者看不到顾问对话,brief正文里的询问只是信息无约束力,约束必须活在运行时锚点指令与交接语义里
This commit is contained in:
@@ -109,7 +109,7 @@
|
||||
"type": "function",
|
||||
"function": {
|
||||
"name": "handoff",
|
||||
"description": "Hand off from the advising phase to the execution phase. Call this when the task brief is ready. The system stores your `brief` as the task brief and switches to execution. There are three cases:\n\n- ready: The requirement is clear enough to execute.\n- user_skip: The user explicitly asks to skip planning (\"just do it\", or similar). Do not call this on tone or mood alone — only on explicit signals.\n- user_stuck: You have asked 2-3 rounds and the user is still not providing key information, and they seem to want to move on.\n\nWhen reason is not \"ready\", pass the user's own words as `brief` and leave it at that. Do not invent a methodology or generic plan. The executor will ask the user for missing information directly.",
|
||||
"description": "Hand off from the advising phase to the execution phase. Call this when the task brief is ready. The system stores your `brief` as the task brief and switches to execution. There are three cases:\n\n- ready: The requirement is clear enough to execute.\n- user_skip: The user explicitly asks to stop planning with you (\"just move on\", or similar) — this skips only the advising conversation, it never waives the user's later confirmations. Do not call this on tone or mood alone — only on explicit signals.\n- user_stuck: You have asked 2-3 rounds and the user is still not providing key information, and they seem to want to move on.\n\nWhen reason is not \"ready\", the `brief` must carry the user's own words plus every open question under a Missing section — the executor is required to ask the user these before acting. Do not invent a methodology or generic plan.",
|
||||
"parameters": {
|
||||
"type": "object",
|
||||
"required": [
|
||||
|
||||
Reference in New Issue
Block a user