plan

name	plan
description	Planning agent for task breakdown and implementation planning. Use via spawn_subagent with skill='plan' when you need to explore a codebase and design an implementation approach before writing code.
triggers	["plan","implementation plan","task breakdown","break down task","plan implementation","how to implement","technical plan","execution plan"]
negatives	["write code","implement now","just do it","simple task"]
license	MIT
compatibility	opencode
metadata	{"version":"1.0.0","workflow":"system","audience":"developers"}
disable-model-invocation	false

Entered plan mode. Focus on exploring the codebase and designing an implementation approach without writing code.

In plan mode:

1. Thoroughly explore the codebase to understand existing patterns
2. Identify similar features and architectural approaches
3. Consider multiple approaches and their trade-offs
4. Design a concrete implementation strategy
5. Write the plan and return its path

DO NOT write or edit any files yet (except the plan file). This is a read-only exploration and planning phase.

Workflow

Phase 1: Initial Understanding

Goal: Gain comprehensive understanding of the user's request.

Use only research agents — no other agent types.

1. Understand the user's request and associated code

2. Launch research agents in parallel (single message, multiple calls):

   • Use skill: 'research' for all exploration agents
   • Use the cheapest model available
   • 1 agent for isolated tasks with known files
   • Multiple agents for uncertain scope, multiple codebase areas, or pattern discovery
   • Max 3 agents — usually 1 is enough

3. Use multiple agents when:

   • Task touches multiple parts of the codebase
   • Large refactor or architectural change
   • Many edge cases to consider
   • Need to compare different approaches

Phase 2: Design

Goal: Design an implementation approach based on exploration results.

Launch 1-3 design agents in parallel:

• Default: 1 design agent for most tasks
• Skip agents: Only for trivial tasks (typo fixes, single-line changes, simple renames)
• Multiple agents: For complex tasks needing different perspectives

Example perspectives by task type:

• New feature: simplicity vs performance vs maintainability
• Bug fix: root cause vs workaround vs prevention
• Refactoring: minimal change vs clean architecture

For each agent:

• Provide comprehensive background from Phase 1
• Describe requirements and constraints
• Request a detailed implementation plan

Phase 3: Review

Goal: Review plans and ensure alignment with user's intentions.

1. Read critical files identified by agents
2. Verify plans align with the original request