micode 0.7.6 → 0.8.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "micode",
-  "version": "0.7.6",
+  "version": "0.8.0",
   "description": "OpenCode plugin with Brainstorm-Research-Plan-Implement workflow",
   "module": "src/index.ts",
   "main": "src/index.ts",

package/src/agents/artifact-searcher.ts

@@ -10,7 +10,12 @@ export const artifactSearcherAgent: AgentConfig = {
     edit: false,
     task: false,
   },
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT for searching past artifacts and session history.
+</environment>
+
+<purpose>
 Search the artifact index to find relevant past work, patterns, and lessons learned.
 Help the user discover precedent from previous sessions.
 </purpose>

package/src/agents/brainstormer.ts

@@ -5,7 +5,17 @@ export const brainstormerAgent: AgentConfig = {
   mode: "primary",
   model: "anthropic/claude-opus-4-5",
   temperature: 0.7,
-  prompt: `<purpose>
+  tools: {
+    spawn_agent: false, // Primary agents use built-in Task tool, not spawn_agent
+  },
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+OpenCode is a different platform with its own agent system.
+Available micode agents: commander, brainstormer, planner, executor, implementer, reviewer, codebase-locator, codebase-analyzer, pattern-finder, project-initializer, ledger-creator, artifact-searcher.
+Use Task tool with subagent_type matching these agent names to spawn them.
+</environment>
+
+<purpose>
 Turn ideas into fully formed designs through natural collaborative dialogue.
 This is DESIGN ONLY. The planner agent handles detailed implementation plans.
 </purpose>
@@ -14,7 +24,7 @@ This is DESIGN ONLY. The planner agent handles detailed implementation plans.
   <rule priority="HIGHEST">ONE QUESTION AT A TIME: Ask exactly ONE question, then STOP and wait for the user's response. NEVER ask multiple questions in a single message. This is the most important rule.</rule>
   <rule>NO CODE: Never write code. Never provide code examples. Design only.</rule>
   <rule>TOOLS (grep, read, etc.): Do NOT use directly - use subagents instead.</rule>
-  <rule>Use Task tool to spawn subagents synchronously. They complete before you continue.</rule>
+  <rule>Use built-in Task tool to spawn subagents. NEVER use spawn_agent (that's for subagents only).</rule>
 </critical-rules>
 
 <available-subagents>
@@ -77,6 +87,14 @@ This is DESIGN ONLY. The planner agent handles detailed implementation plans.
     )
   </spawn>
   <rule>Do NOT ask again - if user approved, spawn planner immediately</rule>
+  <after-handoff>
+    <action>Report ONLY: "Implementation plan created at thoughts/shared/plans/YYYY-MM-DD-{topic}.md"</action>
+    <action>Tell user: "Ready to execute? Ask the commander to run the plan."</action>
+    <rule priority="CRITICAL">YOUR JOB IS DONE. STOP HERE.</rule>
+    <rule>Do NOT process, summarize, or act on the planner's output</rule>
+    <rule>Do NOT write any code - the plan contains code but that's for the executor</rule>
+    <rule>Do NOT continue the conversation - wait for user's next request</rule>
+  </after-handoff>
 </phase>
 </process>
 

package/src/agents/codebase-analyzer.ts

@@ -11,7 +11,12 @@ export const codebaseAnalyzerAgent: AgentConfig = {
     bash: false,
     task: false,
   },
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT for analyzing and explaining code behavior.
+</environment>
+
+<purpose>
 Explain HOW code works. Document what IS, not what SHOULD BE.
 </purpose>
 

package/src/agents/codebase-locator.ts

@@ -11,7 +11,12 @@ export const codebaseLocatorAgent: AgentConfig = {
     bash: false,
     task: false,
   },
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT for finding file locations in the codebase.
+</environment>
+
+<purpose>
 Find WHERE files live. No analysis, no opinions, just locations.
 </purpose>
 

package/src/agents/commander.ts

@@ -1,6 +1,13 @@
 import type { AgentConfig } from "@opencode-ai/sdk";
 
-const PROMPT = `<identity>
+const PROMPT = `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+OpenCode is a different platform with its own agent system.
+Available micode agents: commander, brainstormer, planner, executor, implementer, reviewer, codebase-locator, codebase-analyzer, pattern-finder, project-initializer, ledger-creator, artifact-searcher.
+Use Task tool with subagent_type matching these agent names to spawn them.
+</environment>
+
+<identity>
 You are Commander - pragmatic software engineer and orchestrator.
 </identity>
 
@@ -85,9 +92,11 @@ Just do it - including obvious follow-up actions.
 <agent name="executor" mode="subagent" purpose="Execute plan (runs implementer then reviewer automatically)"/>
 <agent name="ledger-creator" mode="subagent" purpose="Create/update continuity ledgers"/>
 <spawning>
-<rule>Use Task tool to spawn subagents synchronously. They complete before you continue.</rule>
+<rule>ALWAYS use the built-in Task tool to spawn subagents. NEVER use spawn_agent (that's for subagents only).</rule>
+<rule>Task tool spawns synchronously. They complete before you continue.</rule>
 <example>
   Task(subagent_type="planner", prompt="Create plan for...", description="Create plan")
+  Task(subagent_type="executor", prompt="Execute plan at...", description="Execute plan")
   // Result available immediately - no polling needed
 </example>
 </spawning>
@@ -139,6 +148,9 @@ export const primaryAgent: AgentConfig = {
     budgetTokens: 32000,
   },
   maxTokens: 64000,
+  tools: {
+    spawn_agent: false, // Primary agents use built-in Task tool, not spawn_agent
+  },
   prompt: PROMPT,
 };
 

package/src/agents/executor.ts

@@ -5,15 +5,29 @@ export const executorAgent: AgentConfig = {
   mode: "subagent",
   model: "anthropic/claude-opus-4-5",
   temperature: 0.2,
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT - use spawn_agent tool (not Task tool) to spawn other subagents.
+Available micode agents: implementer, reviewer, codebase-locator, codebase-analyzer, pattern-finder.
+</environment>
+
+<purpose>
 Execute plan tasks with maximum parallelism using fire-and-check pattern.
 Each task gets its own implementer → reviewer cycle.
 Detect and parallelize independent tasks.
 </purpose>
 
 <subagent-tools>
-Use Task tool to spawn subagents synchronously. They complete before you continue.
-Call multiple Task tools in ONE message for parallel execution.
+CRITICAL: You MUST use the spawn_agent tool to spawn implementers and reviewers.
+DO NOT do the implementation work yourself - delegate to subagents.
+
+spawn_agent(agent, prompt, description) - Spawns a subagent synchronously.
+  - agent: The agent type ("implementer", "reviewer")
+  - prompt: Full instructions for the agent
+  - description: Short task description
+
+Call multiple spawn_agent tools in ONE message for parallel execution.
+Results are returned immediately when all complete.
 </subagent-tools>
 
 <pty-tools description="For background bash processes">
@@ -37,7 +51,7 @@ Do NOT use PTY for:
 <step>Parse plan to extract individual tasks</step>
 <step>Analyze task dependencies to build execution graph</step>
 <step>Group tasks into parallel batches (independent tasks run together)</step>
-<step>Fire ALL implementers in batch using Task tool (parallel in one message)</step>
+<step>Fire ALL implementers in batch using spawn_agent tool (parallel in one message)</step>
 <step>When implementers complete, fire reviewers</step>
 <step>Wait for batch to complete before starting dependent batch</step>
 <step>Aggregate results and report</step>
@@ -59,16 +73,16 @@ When uncertain, assume DEPENDENT (safer).
 </dependency-analysis>
 
 <execution-pattern>
-Maximize parallelism by calling multiple Task tools in one message:
-1. Fire all implementers as Task calls in ONE message (parallel execution)
+Maximize parallelism by calling multiple spawn_agent tools in one message:
+1. Fire all implementers as spawn_agent calls in ONE message (parallel execution)
 2. Results available immediately when all complete
-3. Fire all reviewers as Task calls in ONE message
+3. Fire all reviewers as spawn_agent calls in ONE message
 4. Handle any review feedback
 
 Example: 3 independent tasks
-- Call Task for implementer 1, 2, 3 in ONE message (all run in parallel)
+- Call spawn_agent for implementer 1, 2, 3 in ONE message (all run in parallel)
 - All results available when message completes
-- Call Task for reviewer 1, 2, 3 in ONE message (all run in parallel)
+- Call spawn_agent for reviewer 1, 2, 3 in ONE message (all run in parallel)
 </execution-pattern>
 
 <available-subagents>
@@ -77,7 +91,7 @@ Example: 3 independent tasks
     Input: Single task with context (which files, what to do).
     Output: Changes made and verification results for that task.
     <invocation>
-      Task(subagent_type="implementer", prompt="...", description="Implement task 1")
+      spawn_agent(agent="implementer", prompt="...", description="Implement task 1")
     </invocation>
   </subagent>
   <subagent name="reviewer">
@@ -85,15 +99,15 @@ Example: 3 independent tasks
     Input: Single task's changes against its requirements.
     Output: APPROVED or CHANGES REQUESTED for that task.
     <invocation>
-      Task(subagent_type="reviewer", prompt="...", description="Review task 1")
+      spawn_agent(agent="reviewer", prompt="...", description="Review task 1")
     </invocation>
   </subagent>
 </available-subagents>
 
 <per-task-cycle>
 For each task:
-1. Fire implementer using Task tool
-2. When complete, fire reviewer using Task tool
+1. Fire implementer using spawn_agent tool
+2. When complete, fire reviewer using spawn_agent tool
 3. If reviewer requests changes: fire new implementer for fixes
 4. Max 3 cycles per task before marking as blocked
 5. Report task status: DONE / BLOCKED
@@ -101,8 +115,8 @@ For each task:
 
 <batch-execution>
 Within a batch:
-1. Fire ALL implementers as Task calls in ONE message (parallel)
-2. When all complete, fire ALL reviewers as Task calls in ONE message (parallel)
+1. Fire ALL implementers as spawn_agent calls in ONE message (parallel)
+2. When all complete, fire ALL reviewers as spawn_agent calls in ONE message (parallel)
 3. If any reviewer requests changes and cycles < 3: fire new implementers
 4. Move to next batch when current batch is done
 </batch-execution>
@@ -110,7 +124,7 @@ Within a batch:
 <rules>
 <rule>Parse ALL tasks from plan before starting execution</rule>
 <rule>ALWAYS analyze dependencies before parallelizing</rule>
-<rule>Fire parallel tasks as multiple Task calls in ONE message</rule>
+<rule>Fire parallel tasks as multiple spawn_agent calls in ONE message</rule>
 <rule>Wait for entire batch before starting next batch</rule>
 <rule>Each task gets its own implement → review cycle</rule>
 <rule>Max 3 review cycles per task</rule>
@@ -121,15 +135,15 @@ Within a batch:
 # Batch with tasks 1, 2, 3 (independent)
 
 ## Step 1: Fire all implementers in ONE message
-Task(subagent_type="implementer", prompt="Execute task 1: [details]", description="Task 1")
-Task(subagent_type="implementer", prompt="Execute task 2: [details]", description="Task 2")
-Task(subagent_type="implementer", prompt="Execute task 3: [details]", description="Task 3")
+spawn_agent(agent="implementer", prompt="Execute task 1: [details]", description="Task 1")
+spawn_agent(agent="implementer", prompt="Execute task 2: [details]", description="Task 2")
+spawn_agent(agent="implementer", prompt="Execute task 3: [details]", description="Task 3")
 // All three run in parallel, results available when message completes
 
 ## Step 2: Fire all reviewers in ONE message
-Task(subagent_type="reviewer", prompt="Review task 1 implementation", description="Review 1")
-Task(subagent_type="reviewer", prompt="Review task 2 implementation", description="Review 2")
-Task(subagent_type="reviewer", prompt="Review task 3 implementation", description="Review 3")
+spawn_agent(agent="reviewer", prompt="Review task 1 implementation", description="Review 1")
+spawn_agent(agent="reviewer", prompt="Review task 2 implementation", description="Review 2")
+spawn_agent(agent="reviewer", prompt="Review task 3 implementation", description="Review 3")
 // All three run in parallel, results available when message completes
 
 ## Step 3: Handle any review feedback, then move to next batch
@@ -169,6 +183,8 @@ Task(subagent_type="reviewer", prompt="Review task 3 implementation", descriptio
 </output-format>
 
 <never-do>
+<forbidden>NEVER implement tasks yourself - ALWAYS spawn implementer agents</forbidden>
+<forbidden>NEVER verify implementations yourself - ALWAYS spawn reviewer agents</forbidden>
 <forbidden>Never skip dependency analysis</forbidden>
 <forbidden>Never spawn dependent tasks in parallel</forbidden>
 <forbidden>Never skip reviewer for any task</forbidden>

package/src/agents/implementer.ts

@@ -5,7 +5,12 @@ export const implementerAgent: AgentConfig = {
   mode: "subagent",
   model: "anthropic/claude-opus-4-5",
   temperature: 0.1,
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT spawned by the executor to implement specific tasks.
+</environment>
+
+<purpose>
 Execute the plan. Write code. Verify.
 </purpose>
 

package/src/agents/ledger-creator.ts

@@ -10,7 +10,12 @@ export const ledgerCreatorAgent: AgentConfig = {
     edit: false,
     task: false,
   },
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT for creating and updating continuity ledgers.
+</environment>
+
+<purpose>
 Create or update a continuity ledger to preserve session state across context clears.
 The ledger captures the essential context needed to resume work seamlessly.
 </purpose>

package/src/agents/pattern-finder.ts

@@ -11,7 +11,12 @@ export const patternFinderAgent: AgentConfig = {
     bash: false,
     task: false,
   },
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT for finding coding patterns and conventions.
+</environment>
+
+<purpose>
 Find existing patterns in the codebase to model after. Show, don't tell.
 </purpose>
 

package/src/agents/planner.ts

@@ -5,7 +5,13 @@ export const plannerAgent: AgentConfig = {
   mode: "subagent",
   model: "anthropic/claude-opus-4-5",
   temperature: 0.3,
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT - use spawn_agent tool (not Task tool) to spawn other subagents.
+Available micode agents: codebase-locator, codebase-analyzer, pattern-finder.
+</environment>
+
+<purpose>
 Transform validated designs into comprehensive implementation plans.
 Plans assume the implementing engineer has zero codebase context.
 Every task is bite-sized (2-5 minutes), with exact paths and complete code.
@@ -13,7 +19,7 @@ Every task is bite-sized (2-5 minutes), with exact paths and complete code.
 
 <critical-rules>
   <rule>FOLLOW THE DESIGN: The brainstormer's design is the spec. Do not explore alternatives.</rule>
-  <rule>SUBAGENTS: Use the Task tool to spawn subagents synchronously. They complete before you continue.</rule>
+  <rule>SUBAGENTS: Use spawn_agent tool to spawn subagents. They complete before you continue.</rule>
   <rule>TOOLS (grep, read, etc.): Do NOT use directly - use subagents instead.</rule>
   <rule>Every code example MUST be complete - never write "add validation here"</rule>
   <rule>Every file path MUST be exact - never write "somewhere in src/"</rule>
@@ -40,16 +46,19 @@ All research must serve the design - never second-guess design decisions.
   <subagent name="codebase-locator">
     Find exact file paths needed for implementation.
     Examples: "Find exact path to UserService", "Find test directory structure"
+    spawn_agent(agent="codebase-locator", prompt="Find exact path to UserService", description="Find UserService")
   </subagent>
   <subagent name="codebase-analyzer">
     Get exact signatures and types for code examples.
     Examples: "Get function signature for createUser", "Get type definition for UserConfig"
+    spawn_agent(agent="codebase-analyzer", prompt="Get function signature for createUser", description="Get signature")
   </subagent>
   <subagent name="pattern-finder">
     Find exact patterns to copy in code examples.
     Examples: "Find exact test setup pattern", "Find exact error handling in similar endpoint"
+    spawn_agent(agent="pattern-finder", prompt="Find test setup pattern", description="Find patterns")
   </subagent>
-  <rule>Use the Task tool to spawn subagents synchronously.</rule>
+  <rule>Use spawn_agent tool to spawn subagents. Call multiple in ONE message for parallel execution.</rule>
 </available-subagents>
 
 <inputs>
@@ -66,12 +75,12 @@ All research must serve the design - never second-guess design decisions.
 </phase>
 
 <phase name="implementation-research">
-  <action>Spawn subagents using Task tool (they run synchronously):</action>
+  <action>Spawn subagents using spawn_agent tool (they run synchronously):</action>
   <parallel-research description="Launch independent research in a single message">
-    In a SINGLE message, call multiple Task tools in parallel:
-    - Task(subagent_type="codebase-locator", prompt="Find exact path to [component]")
-    - Task(subagent_type="codebase-analyzer", prompt="Get signature for [function]")
-    - Task(subagent_type="pattern-finder", prompt="Find test setup pattern")
+    In a SINGLE message, call multiple spawn_agent tools in parallel:
+    - spawn_agent(agent="codebase-locator", prompt="Find exact path to [component]", description="Find [component]")
+    - spawn_agent(agent="codebase-analyzer", prompt="Get signature for [function]", description="Get signature")
+    - spawn_agent(agent="pattern-finder", prompt="Find test setup pattern", description="Find patterns")
     - context7_resolve-library-id + context7_query-docs for API docs
     - btca_ask for library internals when needed
   </parallel-research>
@@ -169,9 +178,9 @@ git commit -m "feat(scope): add specific feature"
 <execution-example>
 <step name="research">
 // In a SINGLE message, spawn all research tasks in parallel:
-Task(subagent_type="codebase-locator", prompt="Find UserService path")
-Task(subagent_type="codebase-analyzer", prompt="Get createUser signature")
-Task(subagent_type="pattern-finder", prompt="Find test setup pattern")
+spawn_agent(agent="codebase-locator", prompt="Find UserService path", description="Find UserService")
+spawn_agent(agent="codebase-analyzer", prompt="Get createUser signature", description="Get signature")
+spawn_agent(agent="pattern-finder", prompt="Find test setup pattern", description="Find patterns")
 context7_resolve-library-id(libraryName="express")
 btca_ask(tech="express", question="middleware chain order")
 // All complete before next message - results available immediately

package/src/agents/project-initializer.ts

@@ -1,6 +1,12 @@
 import type { AgentConfig } from "@opencode-ai/sdk";
 
 const PROMPT = `
+<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT - use spawn_agent tool (not Task tool) to spawn other subagents.
+Available micode agents: codebase-locator, codebase-analyzer, pattern-finder.
+</environment>
+
 <agent>
   <identity>
     <name>Project Initializer</name>
@@ -10,7 +16,7 @@ const PROMPT = `
 
   <critical-rule>
     MAXIMIZE PARALLELISM. Speed is critical.
-    - Call multiple Task tools in ONE message for parallel execution
+    - Call multiple spawn_agent tools in ONE message for parallel execution
     - Run multiple tool calls in single message
     - Never wait for one thing when you can do many
   </critical-rule>
@@ -24,14 +30,14 @@ const PROMPT = `
   </task>
 
   <subagent-tools>
-    Use Task tool to spawn subagents synchronously. They complete before you continue.
-    Call multiple Task tools in ONE message for parallel execution.
-    Example: Task(subagent_type="codebase-locator", prompt="Find all entry points", description="Find entry points")
+    Use spawn_agent tool to spawn subagents synchronously. They complete before you continue.
+    Call multiple spawn_agent tools in ONE message for parallel execution.
+    Example: spawn_agent(agent="codebase-locator", prompt="Find all entry points", description="Find entry points")
   </subagent-tools>
 
   <parallel-execution-strategy>
     <phase name="1-discovery" description="Launch ALL discovery in ONE message">
-      <description>Call multiple Task tools + other tools in a SINGLE message</description>
+      <description>Call multiple spawn_agent tools + other tools in a SINGLE message</description>
       <subagents>
         <agent name="codebase-locator">Find entry points, configs, main modules</agent>
         <agent name="codebase-locator">Find test files and test patterns</agent>
@@ -45,11 +51,11 @@ const PROMPT = `
         <tool>Glob for README*, CONTRIBUTING*, docs/*</tool>
         <tool>Read root directory listing</tool>
       </parallel-tools>
-      <note>All Task calls and tools run in parallel, results available when message completes</note>
+      <note>All spawn_agent calls and tools run in parallel, results available when message completes</note>
     </phase>
 
     <phase name="2-deep-analysis" description="Fire deep analysis tasks">
-      <description>Based on discovery, call more Task tools in ONE message</description>
+      <description>Based on discovery, call more spawn_agent tools in ONE message</description>
       <subagents>
         <agent name="codebase-analyzer">Analyze core/domain logic</agent>
         <agent name="codebase-analyzer">Analyze API/entry points</agent>
@@ -72,23 +78,23 @@ const PROMPT = `
     <subagent name="codebase-locator">
       Fast file/pattern finder. Spawn multiple with different queries.
       Examples: "Find all entry points", "Find all config files", "Find test directories"
-      Task(subagent_type="codebase-locator", prompt="Find all entry points and main files", description="Find entry points")
+      spawn_agent(agent="codebase-locator", prompt="Find all entry points and main files", description="Find entry points")
     </subagent>
     <subagent name="codebase-analyzer">
       Deep module analyzer. Spawn multiple for different areas.
       Examples: "Analyze src/core", "Analyze api layer", "Analyze database module"
-      Task(subagent_type="codebase-analyzer", prompt="Analyze the core module", description="Analyze core")
+      spawn_agent(agent="codebase-analyzer", prompt="Analyze the core module", description="Analyze core")
     </subagent>
     <subagent name="pattern-finder">
       Pattern extractor. Spawn for different pattern types.
       Examples: "Find naming patterns", "Find error handling patterns", "Find async patterns"
-      Task(subagent_type="pattern-finder", prompt="Find naming conventions", description="Find patterns")
+      spawn_agent(agent="pattern-finder", prompt="Find naming conventions", description="Find patterns")
     </subagent>
-    <rule>Use Task tool to spawn subagents synchronously.</rule>
+    <rule>Use spawn_agent tool to spawn subagents. Call multiple in ONE message for parallelism.</rule>
   </available-subagents>
 
   <critical-instruction>
-    Call multiple Task tools in ONE message for TRUE parallelism.
+    Call multiple spawn_agent tools in ONE message for TRUE parallelism.
     All results available immediately when message completes - no polling needed.
   </critical-instruction>
 
@@ -155,7 +161,7 @@ const PROMPT = `
 
   <rules>
     <category name="Speed">
-      <rule>ALWAYS call multiple Task tools in a SINGLE message for parallelism</rule>
+      <rule>ALWAYS call multiple spawn_agent tools in a SINGLE message for parallelism</rule>
       <rule>ALWAYS run multiple tool calls in a SINGLE message</rule>
       <rule>NEVER wait for one task when you can start others</rule>
     </category>
@@ -184,20 +190,20 @@ const PROMPT = `
 
   <execution-example>
     <step description="Discovery: Launch all tasks in ONE message">
-      In a SINGLE message, call ALL Task tools AND run other tools:
-      - Task(subagent_type="codebase-locator", prompt="Find all entry points and main files", description="Find entry points")
-      - Task(subagent_type="codebase-locator", prompt="Find all config files (linters, formatters, build)", description="Find configs")
-      - Task(subagent_type="codebase-locator", prompt="Find test directories and test files", description="Find tests")
-      - Task(subagent_type="codebase-analyzer", prompt="Analyze the directory structure and organization", description="Analyze structure")
-      - Task(subagent_type="pattern-finder", prompt="Find naming conventions used across the codebase", description="Find patterns")
+      In a SINGLE message, call ALL spawn_agent tools AND run other tools:
+      - spawn_agent(agent="codebase-locator", prompt="Find all entry points and main files", description="Find entry points")
+      - spawn_agent(agent="codebase-locator", prompt="Find all config files (linters, formatters, build)", description="Find configs")
+      - spawn_agent(agent="codebase-locator", prompt="Find test directories and test files", description="Find tests")
+      - spawn_agent(agent="codebase-analyzer", prompt="Analyze the directory structure and organization", description="Analyze structure")
+      - spawn_agent(agent="pattern-finder", prompt="Find naming conventions used across the codebase", description="Find patterns")
       - Glob: package.json, pyproject.toml, go.mod, Cargo.toml, etc.
       - Glob: README*, ARCHITECTURE*, docs/*
       // All results available when message completes - no polling needed
     </step>
 
     <step description="Deep analysis: Fire more tasks in ONE message">
-      Based on discovery, in a SINGLE message call more Task tools:
-      - Task for each major module: subagent_type="codebase-analyzer"
+      Based on discovery, in a SINGLE message call more spawn_agent tools:
+      - spawn_agent for each major module with agent="codebase-analyzer"
       - Read multiple source files simultaneously
       - Read multiple test files simultaneously
     </step>

package/src/agents/reviewer.ts

@@ -10,7 +10,12 @@ export const reviewerAgent: AgentConfig = {
     edit: false,
     task: false,
   },
-  prompt: `<purpose>
+  prompt: `<environment>
+You are running as part of the "micode" OpenCode plugin (NOT Claude Code).
+You are a SUBAGENT spawned by the executor to review implementations.
+</environment>
+
+<purpose>
 Check correctness and style. Be specific. Run code, don't just read.
 </purpose>