Upload 3 files
Browse files
PlanGeneratorAtomicFlow.yaml
CHANGED
|
@@ -4,11 +4,9 @@ enable_cache: True
|
|
| 4 |
|
| 5 |
input_interface_non_initialized: # initial input keys
|
| 6 |
- "goal"
|
| 7 |
-
- "memory_files" # In planner of extlib, it should be an empty dict.
|
| 8 |
|
| 9 |
input_interface_initialized: # input_keys
|
| 10 |
- "goal"
|
| 11 |
-
- "memory_files"
|
| 12 |
|
| 13 |
#######################################################
|
| 14 |
# Output keys
|
|
@@ -23,15 +21,17 @@ system_message_prompt_template:
|
|
| 23 |
template: |2-
|
| 24 |
You are a planner of a coding department, your task is to make a step-by-step plan for the coders to follow, inorder to solve the task.
|
| 25 |
|
| 26 |
-
The coding department is only able to write functions, at a higher level, your job is to
|
| 27 |
|
| 28 |
The details of your task are:
|
| 29 |
-
1.
|
| 30 |
2. Upon feedback of the plan from the user, make refinements based on the feedback.
|
| 31 |
|
| 32 |
Notice that:
|
| 33 |
1. If the goal given to you is simple enough that is doable within one function, it is okay that your plan only has one step.
|
| 34 |
2. If the goal involves several feature to implement or has several milestones to reach, decompose it into atomic and modular steps of a plan.
|
|
|
|
|
|
|
| 35 |
|
| 36 |
The coding department is able to access the Internet, so it may be useful to use some online services via APIs.
|
| 37 |
|
|
@@ -49,7 +49,7 @@ system_message_prompt_template:
|
|
| 49 |
|
| 50 |
Performance Evaluation:
|
| 51 |
1. Your plan must be as explicit, well-indented, and human-readable as possible.
|
| 52 |
-
2. Your plan must be step-by-step with number indexes.
|
| 53 |
3. You should make plans with as few steps as possible.
|
| 54 |
|
| 55 |
**It's important that you should only respond in JSON format as described below:**
|
|
|
|
| 4 |
|
| 5 |
input_interface_non_initialized: # initial input keys
|
| 6 |
- "goal"
|
|
|
|
| 7 |
|
| 8 |
input_interface_initialized: # input_keys
|
| 9 |
- "goal"
|
|
|
|
| 10 |
|
| 11 |
#######################################################
|
| 12 |
# Output keys
|
|
|
|
| 21 |
template: |2-
|
| 22 |
You are a planner of a coding department, your task is to make a step-by-step plan for the coders to follow, inorder to solve the task.
|
| 23 |
|
| 24 |
+
The coding department is only able to write functions, at a higher level, your job is to tell what function to write at each step.
|
| 25 |
|
| 26 |
The details of your task are:
|
| 27 |
+
1. Decompose the goal into step-by-step plans, each step should contain full information about what function to write, do not decompose an action of writing one function into more than one step.
|
| 28 |
2. Upon feedback of the plan from the user, make refinements based on the feedback.
|
| 29 |
|
| 30 |
Notice that:
|
| 31 |
1. If the goal given to you is simple enough that is doable within one function, it is okay that your plan only has one step.
|
| 32 |
2. If the goal involves several feature to implement or has several milestones to reach, decompose it into atomic and modular steps of a plan.
|
| 33 |
+
3. **Only instruct the coders to write functions, do not write plans about running the functions or returning results.**
|
| 34 |
+
4. **If you instruct the coders to write a function, provide full instructions of writing the funtion in one single step.**
|
| 35 |
|
| 36 |
The coding department is able to access the Internet, so it may be useful to use some online services via APIs.
|
| 37 |
|
|
|
|
| 49 |
|
| 50 |
Performance Evaluation:
|
| 51 |
1. Your plan must be as explicit, well-indented, and human-readable as possible.
|
| 52 |
+
2. Your plan must be step-by-step with number indexes, each step gives full details of writing a function.
|
| 53 |
3. You should make plans with as few steps as possible.
|
| 54 |
|
| 55 |
**It's important that you should only respond in JSON format as described below:**
|