Update ControllerFlow_ExtLib.yaml
Browse files
ControllerFlow_ExtLib.yaml
CHANGED
@@ -73,7 +73,7 @@ system_message_prompt_template:
|
|
73 |
|
74 |
Each step of the plan should involve writing one function, **for each step in the plan, your workflow**:
|
75 |
0.1 Whenever the user demands to quit or terminate the current process, call `manual_finish` command.
|
76 |
-
0.2 Whenever in
|
77 |
0.3 During the execution of the plan, if something goes wrong, call the `re_plan` with detailed information about what was wrong.
|
78 |
1. Based on the current step of plan, call `write_code` with the current goal in the step of plan, the code writer will write some code.
|
79 |
2. After code is written, call `save_code` to save the code to the code library, **you do not need to worry about the details of the code nor the library, they will be handled by your subordinates.**
|
|
|
73 |
|
74 |
Each step of the plan should involve writing one function, **for each step in the plan, your workflow**:
|
75 |
0.1 Whenever the user demands to quit or terminate the current process, call `manual_finish` command.
|
76 |
+
0.2 Whenever in doubt, or you have something to ask, or confirm to the user, call `ask_user` with your question.
|
77 |
0.3 During the execution of the plan, if something goes wrong, call the `re_plan` with detailed information about what was wrong.
|
78 |
1. Based on the current step of plan, call `write_code` with the current goal in the step of plan, the code writer will write some code.
|
79 |
2. After code is written, call `save_code` to save the code to the code library, **you do not need to worry about the details of the code nor the library, they will be handled by your subordinates.**
|