You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agent/run_agent.py
+6-6Lines changed: 6 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -346,18 +346,18 @@ def run_team_for_repo(
346
346
yaml.dump(agent_config, agent_config_file)
347
347
348
348
# /ask will make aider not write any code, but only a plan
349
-
manager_message=f"""You are a manager in charge of writing a plan to complete the implementations for all functions (i.e., those with pass statements) and pass the unit tests. Write a concise plan of attack to implement the entire repo, but don't actually do any coding. Please output the plan in the format of a list of numbered steps. Each step should specify a file to edit and a high-level description of the change to make. Note that we only need to edit the files that contain functions with pass statements, ie. those in the current context. Give me only the plan, with no extraneous text.
349
+
manager_message=f"""You are a manager in charge of writing a plan to complete the implementations for all functions (i.e., those with pass statements) and pass the unit tests. Write a plan of attack to implement the entire repo, keeping in mind the most effective order in which tasks should be implemented. Please output the plan in the format of a list of numbered steps. Each step should specify a file to edit and a high-level description of the change to make. Note that we only need to edit the files that contain functions with pass statements, ie. those in the current context. Give me ONLY the plan, with no extraneous text.
350
350
351
-
You MUST precede the plan with the keyword PLAN_START, and end it with the keyword PLAN_END. You MUST follow the formatting of the example plan below, with a number preceding each step on a new line, and one file name followed by a colon and a description of the change to make:
351
+
You MUST precede the plan with the keyword PLAN_START, and end it with the keyword PLAN_END. You MUST follow the formatting of the example plan below, with a number preceding each step on a new line, and one file name followed by a colon and a detailed description of the change to make:
352
352
353
353
PLAN_START
354
-
1.) example_file.py: description of function(s) to implement in example_file.py
355
-
2.) example_file2.py: description of function(s) to implement in example_file2.py
354
+
1.) example_file.py: description of function(s) to implement in example_file.py, including any relevant context or dependencies
355
+
2.) example_file2.py: description of function(s) to implement in example_file2.py, including any relevant context or dependencies
356
356
...
357
357
PLAN_END
358
358
359
359
Remember that you must modify all of the target edit files: {target_edit_files}
360
-
The plan does not neccessarily need to edit the whole file in one step, and it may be more granular as you see fit.
360
+
The plan does not neccessarily need to edit the whole file in one step, and it may be more granular as you see fit. Additionally, you should look at the file 'spec.pdf' for more information on the project requirements and specifications.
0 commit comments