Update Controller_CoderFlow.yaml
Browse files
Controller_CoderFlow.yaml
CHANGED
|
@@ -86,7 +86,7 @@ system_message_prompt_template:
|
|
| 86 |
2.2. The current step of plan requires to import and run some functions from the library. In this case you **MUST** make sure you import the library, something like `from LIBRARY_NAME import FUNCTION_NAME` should suffice.
|
| 87 |
2.3. You need to download a package to the current environment, e.g. `pip install PACKAGE_NAME`, in this case the language of code should be `shell`.
|
| 88 |
After the code is run, the user will provide feedback about the execution, react to the feedback accordingly.
|
| 89 |
-
3. Whenever you have done one step of the plan, do the following:
|
| 90 |
3.1 Reflect on what plan you are having right now.
|
| 91 |
3.2 Reflect on which step of the plan you just finished.
|
| 92 |
3.3 Generate a plan, **it is exactly the same as the plan you have now, but with the current step of plan marked as done**
|
|
@@ -94,7 +94,7 @@ system_message_prompt_template:
|
|
| 94 |
4. Proceed to the next step of the plan, go back to workflow 1 or 2.
|
| 95 |
5. When every step of the plan is done, call the `finish` command, with a summary of what was done.
|
| 96 |
|
| 97 |
-
**You MUST call `update_plan` whenever you realize one step of the plan is done.**
|
| 98 |
|
| 99 |
Here is an example of execution:
|
| 100 |
### Beginning of an example execution: ###
|
|
|
|
| 86 |
2.2. The current step of plan requires to import and run some functions from the library. In this case you **MUST** make sure you import the library, something like `from LIBRARY_NAME import FUNCTION_NAME` should suffice.
|
| 87 |
2.3. You need to download a package to the current environment, e.g. `pip install PACKAGE_NAME`, in this case the language of code should be `shell`.
|
| 88 |
After the code is run, the user will provide feedback about the execution, react to the feedback accordingly.
|
| 89 |
+
3. Whenever you have done one step of the plan, **it could be either extending the library or running the code**, do the following:
|
| 90 |
3.1 Reflect on what plan you are having right now.
|
| 91 |
3.2 Reflect on which step of the plan you just finished.
|
| 92 |
3.3 Generate a plan, **it is exactly the same as the plan you have now, but with the current step of plan marked as done**
|
|
|
|
| 94 |
4. Proceed to the next step of the plan, go back to workflow 1 or 2.
|
| 95 |
5. When every step of the plan is done, call the `finish` command, with a summary of what was done.
|
| 96 |
|
| 97 |
+
**You MUST call `update_plan` whenever you realize one step of the plan, for example, extending the library or running the code is done.**
|
| 98 |
|
| 99 |
Here is an example of execution:
|
| 100 |
### Beginning of an example execution: ###
|