Skip to content

Commit 2f297b3

Browse files
committed
docs:补充关于参数化构建要求检查的说明以确保严格完成任务
1 parent ce379f8 commit 2f297b3

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

  • agents/matmaster_agent/flow_agents/all_finished_agent

agents/matmaster_agent/flow_agents/all_finished_agent/prompt.py

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,10 @@ def create_all_finished_instruction(user_request, history_steps, session_files):
2020
IMPORTANT: If the user_request asks for multiple distinct items/entities/examples (e.g., "caffeine and adenosine",
2121
"A and B", "compare X vs Y", "generate N variants"), the goal is finished ONLY when *all* requested items are completed.
2222
Do NOT mark finished=true when only one of the requested items has been produced.
23+
IMPORTANT: Treat parameterized build requirements (e.g., number of layers, vacuum thickness, slab orientation/cut,
24+
and supercell/expansion such as "expand 5×5×1") as mandatory sub-requirements. finished=true ONLY if history_steps
25+
explicitly shows these parameters were applied, not just that a structure was built.
26+
2327
# Input
2428
history_steps is a list. Each element is a past tool invocation record, typically including
2529
(but not limited to):
@@ -50,6 +54,9 @@ def create_all_finished_instruction(user_request, history_steps, session_files):
5054
5) If there are contradictions in history_steps, prefer the later entries. If you still cannot decide, return finished=false
5155
and explain the contradiction in reason.
5256
6) Do NOT assume results that are not explicitly supported by history_steps or session_files. Judge only from verifiable evidence.
57+
6.1) When user_request includes explicit numeric/parameter constraints (e.g., "cut 5 layers", "vacuum = 1 layer",
58+
"supercell/expand = 5×5×1"), you MUST verify history_steps explicitly confirms each constraint was applied
59+
(e.g., args/output mentions 5 layers + vacuum + 5×5×1). If any one is not explicitly evidenced, set finished=false.
5360
7) Termination/Unachievable rule: If the goal is clearly unachievable given the current context (e.g., repeated critical failures with no viable next action, missing required inputs that cannot be obtained from history_steps/session_files, or hard constraints prevent completion), you MUST return finished=true to terminate, and set reason to explicitly state that the task is not completed but cannot be completed (include the key blocking evidence).
5461
# Output Format (very important)
5562
You must output ONLY ONE JSON object that strictly matches this schema:

0 commit comments

Comments
 (0)