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
@@ -79,9 +81,9 @@ The user asks you to implement a new feature. You respond in multiple steps:
79
81
80
82
1. Spawn a file explorer with different prompts to find relevant files; spawn a find-all-referencer to find more relevant files and answer questions about the codebase; spawn 1 docs research to find relevant docs;
81
83
1a. Read all the relevant files using the read_files tool.
82
-
2. Spawn one more file explorer and one more find-all-referencer with different prompts to find relevant files; spawn a decomposing thinker with questions on a key decision; spawn a decomposing thinker to plan out the feature part-by-part.
84
+
2. Spawn one more file explorer and one more find-all-referencer with different prompts to find relevant files; spawn a decomposing thinker with questions on a key decision; spawn a decomposing thinker to plan out the feature part-by-part. Spawn a code sketcher to sketch out one key section of the code that is the most important or difficult.
83
85
2a. Read all the relevant files using the read_files tool.
84
-
3. Spawn a decomposing thinker to answer final design and implementation questions.
86
+
3. Spawn a decomposing thinker to answer final design and implementation questions and critique the code sketch that was produced. Spawn one more code sketcher to sketch another key section.
85
87
4. Spawn two editors to implement all the changes.
86
88
5. Spawn a reviewer to review the changes made by the editors.
87
89
@@ -99,7 +101,7 @@ The user asks you to implement a new feature. You respond in multiple steps:
99
101
- **Be careful about terminal commands:** Be careful about instructing subagents to run terminal commands that could be destructive or have effects that are hard to undo (e.g. git push, running scripts that could alter production environments, installing packages globally, etc). Don't do any of these unless the user explicitly asks you to.
100
102
`,
101
103
102
-
stepPrompt: `Don't forget to spawn agents that could help, especially: the file-explorer and find-all-referencer to get codebase context, the decomposing thinker to think about key decisions, and the reviewer to review code changes made by the editor.`,
104
+
stepPrompt: `Don't forget to spawn agents that could help, especially: the file-explorer and find-all-referencer to get codebase context, the decomposing thinker to think about key decisions, the code sketcher to sketch out the key sections of code, and the reviewer/decomposing-reviewer to review code changes made by the editor(s).`,
'Writes full implementation plans with complete code changes. Cannot use tools to edit files - instead describes all changes using markdown code blocks. Does not spawn other agents.',
10
+
'Spawn to sketch the code that will be needed to accomplish the task, focusing on the the key sections of logic or interfaces. Cannot use tools to edit files - instead describes all changes using markdown code blocks. Does not spawn other agents.',
11
11
inputSchema: {
12
12
prompt: {
13
13
type: 'string',
14
-
description: 'The coding task to implement',
14
+
description: 'The coding task to sketch out, including the key sections of logic or interfaces it should focus on.',
instructionsPrompt: `You are an expert programmer who writes complete code implementations.
23
+
instructionsPrompt: `You are an expert programmer who sketches out the code that will be needed to accomplish the task.
24
24
25
25
You do not have access to tools to modify files. Instead, you describe all code changes using markdown code blocks.
26
26
27
27
Instructions:
28
28
- Think about the best way to accomplish the task
29
-
- Write out the implementation for each file that needs to be changed
29
+
- Write out the sketch for each file that needs to be changed
30
30
- Use markdown code blocks with the file path as the language identifier
31
31
- For each file, show the only the code changes needed, don't include the entire file
32
32
33
+
Important: Focus on the key sections of logic or interfaces that are needed to accomplish the task! You don't need to sketch out the more obvious parts of the code.
34
+
You can skip over parts of the code using psuedo code or placeholder comments.
35
+
33
36
Guidelines:
34
37
- Pay close attention to the user's request and address all requirements
35
38
- Focus on the simplest solution that accomplishes the task
@@ -40,9 +43,12 @@ Guidelines:
40
43
- Do not add try/catch blocks unless needed
41
44
- Do not write duplicate code that could use existing helpers
0 commit comments