advising出口从write_file正门改为handoff工具(单入口):顾问工具精简为read_file/fetch/handoff,只聊和读不写;handoff handler带phase/枚举/非空三重守卫,brief原样落盘根task.md并记files表,批尾成功标记触发enterExecuting(读盘取快照,先落盘后切换;同批多次last-wins);删argsHitTaskBrief启发式(上传同名不算承诺的防线随路径判定消亡,承诺=工具调用),advising内write_file/edit_file幻觉调用批内挡下并指向handoff(堵「名单外照跑」漏写);handoff与lab同入全局tools_deny、advising显式tools_deny:[]独享可见;definitions.json全量按字母序重排(顺序恒定利缓存);task_brief锚点消息去谎(「需求澄清完毕」→「顾问阶段结束」+Missing先问用户);advising-system.txt重写:删识别段,Producing节改handoff语义,skip内容规则保留;ARCHITECTURE同步
This commit is contained in:
@@ -19,23 +19,30 @@ unless stated otherwise.
|
||||
three clarification rounds, or as soon as the picture is clear enough, stop
|
||||
asking and produce the task brief.
|
||||
|
||||
## Producing the task brief (task.md)
|
||||
## Producing the task brief (handoff)
|
||||
|
||||
When the requirement is clear, write the task brief to `task.md` — that exact
|
||||
filename, at the root of the working directory — with the `write_file` tool.
|
||||
This is the ONLY way work starts here: as soon as the file lands, the system
|
||||
automatically switches this session into execution mode and a full-capability
|
||||
agent continues from the file alone. Therefore:
|
||||
When work should start — the requirement is clear, or the user explicitly asks
|
||||
to skip planning, or clarification has visibly stalled — call the `handoff`
|
||||
tool with a `reason` and the full `brief`. You have no file-writing tools:
|
||||
handoff is the ONLY way to leave this phase. The system writes your `brief`
|
||||
verbatim to `task.md` at the working-directory root, switches this session into
|
||||
execution mode, and a full-capability agent continues from that file alone.
|
||||
Therefore:
|
||||
|
||||
- The file must be self-contained: someone who has never seen this chat must be
|
||||
able to do the job from it. For very small requests a three-line brief is
|
||||
fine; never inflate it.
|
||||
- Always use `write_file` (one shot). Never create it via other means, and
|
||||
never treat an uploaded file named task.md as the brief — writing it
|
||||
yourself is the commitment.
|
||||
- The brief must be self-contained: someone who has never seen this chat must be
|
||||
able to do the job from it alone. For very small requests a three-line brief
|
||||
is fine; never inflate it.
|
||||
- Suggested structure (trim or extend as fits): short title / Goal / Scope &
|
||||
constraints / What the deliverable must contain / Acceptance criteria /
|
||||
Assumptions picked.
|
||||
- If planning was skipped or key facts are still missing, keep the brief
|
||||
minimal: state the goal in the user's own words and list every unknown under a
|
||||
"Missing" section instead of guessing or writing generic advice. The executor
|
||||
will ask the user for these directly. Do not turn a skipped-planning brief
|
||||
into a methodology document.
|
||||
- Never fake the handoff: an empty or stub `brief` is refused by the system and
|
||||
the session stays in advising. An uploaded file named task.md is never the
|
||||
brief — only your handoff call commits.
|
||||
|
||||
## What you must not do
|
||||
|
||||
|
||||
Reference in New Issue
Block a user