Orchestrator tweaks

Author: jahooma

.agents/orchestrator/orchestrator.ts

@@ -28,15 +28,15 @@ const definition: SecretAgentDefinition = {
   },
   outputMode: 'last_message',
   includeMessageHistory: true,
-  toolNames: ['spawn_agents', 'read_files', 'str_replace', 'write_file'],
+  toolNames: ['spawn_agents'],
   spawnableAgents: [
     'read-only-commander',
     'researcher-file-explorer',
     'researcher-web',
     'researcher-docs',
     'decomposing-planner',
     'editor',
-    'reviewer-lite',
+    'reviewer-max',
     'context-pruner',
   ],
 
@@ -55,6 +55,9 @@ const definition: SecretAgentDefinition = {
 - **Proactiveness:** Fulfill the user's request thoroughly, including reasonable, directly implied follow-up actions.
 - **Confirm Ambiguity/Expansion:** Do not take significant actions beyond the clear scope of the request without confirming with the user. If asked *how* to do something, explain first, don't just do it.
 
+${PLACEHOLDER.FILE_TREE_PROMPT_SMALL}
+${PLACEHOLDER.KNOWLEDGE_FILES_CONTENTS}
+
 # Starting Git Changes
 
 The following is the state of the git repository at the start of the conversation. Note that it is not updated to reflect any subsequent changes made by the user or the agents.
@@ -64,23 +67,23 @@ ${PLACEHOLDER.GIT_CHANGES_PROMPT}
 
   instructionsPrompt: `Orchestrate the completion of the coding task using your specialized sub-agents.
 
-## Simple workflow
+## Example workflow
 
 Use this workflow to solve a medium or complex coding task:
 1. Spawn a researcher
 2. Spawn a decomposing planner to come up with a plan.
 3. Spawn an editor to implement the plan.
 4. Spawn a reviewer to review the code. If changes are needed, go back to step 3, but only once.
-5. You must stop before spawning too many sequential agents, becase that this takes too much time and the user will get impatient.
+5. You must stop before spawning too many sequential agents, because that this takes too much time and the user will get impatient.
 
 Feel free to modify this workflow as needed. It's good to spawn different agents in sequence: spawn a researcher before a planner because then the planner can use the researcher's results to come up with a better plan. You can however spawn mulitple researchers, planners, and editors at the same time if needed.
 
 ## Guidelines
 
 - You can spawn agents to help you complete the task. Iterate by spawning more agents as needed.
 - Don't mastermind the task. Rely on your agents' judgement to research, plan, edit, and review the code.
-- Give as many instructions upfront as possible to each agent so you're less likely to need to spawn them again.
 - You should feel free to stop and ask the user for guidance if you're stuck or don't know what to try next, or need a clarification.
+- Give as many instructions upfront as possible to each agent so you're less likely to need to spawn them again.
 - 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 much context.
 - 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.
 `,

.agents/planners/decomposing-planner.ts

@@ -8,7 +8,7 @@ const definition: SecretAgentDefinition = {
   id: 'decomposing-planner',
   publisher,
   model: 'anthropic/claude-sonnet-4.5',
-  displayName: 'Decomposing Planner',
+  displayName: 'Peter Plan',
   spawnerPrompt:
     'Creates the best possible implementation plan by decomposing the task into smaller plans in parallel and synthesizing them into a final plan. Includes full code changes.',
   inputSchema: {