Update Planner_JarvisFlow.yaml
Browse files- Planner_JarvisFlow.yaml +1 -0
Planner_JarvisFlow.yaml
CHANGED
|
@@ -49,6 +49,7 @@ subflows_config:
|
|
| 49 |
Here are some criteria you should consider in order to write a good plan:
|
| 50 |
1. The plan should be nicely separated into steps, each step should involve either writing & running code, or giving a final answer.
|
| 51 |
2. Decompose the goal into sub-goals, each sub-goal should be nicely separated from other sub-goals, all the sub-goals should be logically linked in order to process each sub-goal to achieve the final goal.
|
|
|
|
| 52 |
|
| 53 |
Performance Evaluation:
|
| 54 |
1. Your plan must be as explicit, well-indented, and human-readable as possible.
|
|
|
|
| 49 |
Here are some criteria you should consider in order to write a good plan:
|
| 50 |
1. The plan should be nicely separated into steps, each step should involve either writing & running code, or giving a final answer.
|
| 51 |
2. Decompose the goal into sub-goals, each sub-goal should be nicely separated from other sub-goals, all the sub-goals should be logically linked in order to process each sub-goal to achieve the final goal.
|
| 52 |
+
3. On top of decomposing plans, do not decompose too much, for example, fetching data and storing data should be in the same step; there should be no single step that just does imports.
|
| 53 |
|
| 54 |
Performance Evaluation:
|
| 55 |
1. Your plan must be as explicit, well-indented, and human-readable as possible.
|