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: .agents/base2/base2-with-planner-pro.ts
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ export const createBase2: (
41
41
'researcher-web',
42
42
'researcher-docs',
43
43
'commander',
44
-
'create-plan-gpt-5-pro',
44
+
'planner-pro',
45
45
'code-reviewer',
46
46
'validator',
47
47
'context-pruner',
@@ -61,7 +61,7 @@ Continue to spawn layers of agents until have completed the user's request or re
61
61
62
62
- **Sequence agents properly:** Keep in mind dependencies when spawning different agents. Don't spawn agents in parallel that depend on each other. Be conservative sequencing agents so they can build on each other's insights:
63
63
- Spawn file pickers, code-searcher, directory-lister, glob-matcher, commanders, and researchers before making edits.
64
-
- Spawn create-plan-gpt-5-pro agent after you have gathered all the context you need (and not before!).
64
+
- Spawn planner-pro agent after you have gathered all the context you need (and not before!).
65
65
- Only make edits after generating a plan.
66
66
- Code reviewers/validators should be spawned after you have made your edits.
67
67
- **No need to include context:** When prompting an agent, realize that many agents can already see the entire conversation history, so you can be brief in prompting them without needing to include context.
@@ -128,13 +128,13 @@ The user asks you to implement a new feature. You respond in multiple steps:
128
128
1a. Read all the relevant files using the read_files tool.
129
129
2. Spawn one more file-picker-max and one more code-searcher with different prompts to find relevant files.
130
130
2a. Read all the relevant files using the read_files tool.
131
-
3. Important: Spawn a create-plan-gpt-5-pro agent to generate a plan for the changes.
131
+
3. Important: Spawn a planner-pro agent to generate a plan for the changes.
132
132
4. Use the str_replace or write_file tool to make the changes.
133
133
5. Spawn a code-reviewer to review the changes. Consider making changes suggested by the code-reviewer.
134
134
6. Spawn a validator to run validation commands (tests, typechecks, etc.) to ensure the changes are correct.
135
135
7. Inform the user that you have completed the task in one sentence without a final summary.`,
136
136
137
-
stepPrompt: `Don't forget to spawn agents that could help, especially: the file-picker-max and find-all-referencer to get codebase context, the base2-gpt-5-planner agent to create a plan, the code reviewer to review changes, and the validator to run validation checks.`,
137
+
stepPrompt: `Don't forget to spawn agents that could help, especially: the file-picker-max and find-all-referencer to get codebase context, the planner-pro agent to create a plan, the code reviewer to review changes, and the validator to run validation checks.`,
138
138
139
139
handleSteps: function*({ prompt, params }){
140
140
letsteps=0
@@ -157,5 +157,5 @@ The user asks you to implement a new feature. You respond in multiple steps:
0 commit comments