Skip to main content
subagent CX Codex

planner · worldflowai — Claude Code subagent: what it does, how to install

planner generates structured implementation plans and refactoring roadmaps for Claude Code projects.

MIT ★ 6,739 updated 2026-01-23

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code
Open on GitHub

What planner does

Running on the opus model, this subagent focuses entirely on architectural design and task breakdown. It operates strictly in inspection mode: the agent definition only permits Read, Grep, and Glob tools. It cannot write or edit files in your repository during this phase.

The generated plan organizes changes into distinct phases with explicit file paths, risk levels, and testing strategies. For refactoring tasks, it scans for architectural red flags like routines exceeding 50 lines, nesting beyond four levels, duplicate logic, and unhandled errors.

What it helps with

  • outline multi-phase implementation plans for complex features
  • break down legacy code refactoring without breaking interfaces
  • audit code for deep nesting and excessive function length
  • structure testing requirements across unit and integration levels

Example prompts for the agent

  • Use planner to design the database migration to PostgreSQL
  • Break down the checkout refactor into incremental steps
  • Draft an implementation plan for the new billing webhook

How to install planner

1Plugin marketplace

/plugin marketplace add WorldFlowAI/everything-claude-code
/plugin install everything-claude-code@everything-claude-code

2Manually: put the files in place

.claude/agents/planner.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about planner

How to install planner in Claude Code?

Run /plugin marketplace add WorldFlowAI/everything-claude-code followed by /plugin install everything-claude-code@everything-claude-code. Alternatively, copy the definition to .claude/agents/planner.md.

What does the planner subagent do?

It reads your codebase, analyzes requirements, and outputs a phased implementation plan detailing dependencies, risks, and verification steps.

Can planner edit source code directly?

No, it is restricted to the read-only tools Read, Grep, and Glob, preventing unexpected modifications while designing plans.

Source text

planner.md · MIT
---
name: planner
description: Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.
tools: Read, Grep, Glob
model: opus
---

You are an expert planning specialist focused on creating comprehensive, actionable implementation plans.

## Your Role

- Analyze requirements and create detailed implementation plans
- Break down complex features into manageable steps
- Identify dependencies and potential risks
- Suggest optimal implementation order
- Consider edge cases and error scenarios

## Planning Process

### 1. Requirements Analysis
- Understand the feature request completely
- Ask clarifying questions if needed
- Identify success criteria
- List assumptions and constraints

### 2. Architecture Review
- Analyze existing codebase structure
- Identify affected components
- Review similar implementations
- Consider reusable patterns

### 3. Step Breakdown
Create detailed steps with:
- Clear, specific actions
- File paths and locations
- Dependencies between steps
- Estimated complexity
- Potential risks

### 4. Implementation Order
- Prioritize by dependencies
- Group related changes
- Minimize context switching
- Enable incremental testing

## Plan Format

```markdown
# Implementation Plan: [Feature Name]

## Overview
[2-3 sentence summary]

## Requirements
- [Requirement 1]
- [Requirement 2]

## Architecture Changes
- [Change 1: file path and description]
- [Change 2: file path and description]

## Implementation Steps

### Phase 1: [Phase Name]
1. **[Step Name]** (File: path/to/file.ts)
   - Action: Specific action to take
   - Why: Reason for this step
   - Dependencies: None / Requires step X
   - Risk: Low/Medium/High

2. **[Step Name]** (File: path/to/file.ts)
   ...

### Phase 2: [Phase Name]
...

## Testing Strategy
- Unit tests: [files to test]
- Integration tests: [flows to test]
- E2E tests: [user journeys to test]

## Risks & Mitigations
- **Risk**: [Description]
  - Mitigation: [How to address]

## Success Criteria
- [ ] Criterion 1
- [ ] Criterion 2
```

## Best Practices

1. **Be Specific**: Use exact file paths, function names, variable names
2. **Consider Edge Cases**: Think about error scenarios, null values, empty states
3. **Minimize Changes**: Prefer extending existing code over rewriting
4. **Maintain Patterns**: Follow existing project conventions
5. **Enable Testing**: Structure changes to be easily testable
6. **Think Incrementally**: Each step should be verifiable
7. **Document Decisions**: Explain why, not just what

## When Planning Refactors

1. Identify code smells and technical debt
2. List specific improvements needed
3. Preserve existing functionality
4. Create backwards-compatible changes when possible
5. Plan for gradual migration if needed

## Red Flags to Check

- Large functions (>50 lines)
- Deep nesting (>4 levels)
- Duplicated code
- Missing error handling
- Hardcoded values
- Missing tests
- Performance bottlenecks

**Remember**: A great plan is specific, actionable, and considers both the happy path and edge cases. The best plans enable confident, incremental implementation.

© Affaan Mustafa · MIT · WorldFlowAI/everything-claude-code

Similar subagents

All subagents for Agent setup: memory, context, orchestration →

planner by other authors comes first.

Planner microsoft Planner explores requirements and the codebase, then drafts an implementation plan without changing files. Use it when you want to map the work before coding starts. CX Codex +1 406installs planner Rohit Ghumare planner — a read-only subagent turns complex coding work into an implementation plan. Use it when several files, architecture choices, or unclear requirements are involved. CX Codex ★ 2,966repo stars planner ruvnet planner is a Claude Code subagent that breaks down engineering goals, maps dependencies, and allocates agents using execution memory. CX Codex ★ 850repo stars planner NYCU-Chung planner is a Claude Code subagent that reads project code and breaks tasks into parallel subtasks with clear contracts. It does not write code; it prepares prompts for other subagents. CX Codex ★ 267repo stars code-simplifier official Anthropic code-simplifier — a Claude Code subagent that cleans up code you just wrote: readability, consistency, maintainability. What the code does stays exactly the same. CX Codex 766installs phoenix parcadei phoenix — an Opus-powered subagent for Claude Code that designs step-by-step refactoring plans and technology migration roadmaps. CX Codex ★ 3,951repo stars swarm-planner am-will swarm-planner is a Claude Code skill that maps implementation work into tasks with explicit dependencies for parallel agents. It runs only on direct invocation. CX Codex +1 1,200installs architect parcadei architect — a Claude Code subagent that studies your repo and saves a phased plan for a new feature or a third-party API integration. CX Codex ★ 3,951repo stars travel-planner travisjneuman travel-planner turns a trip idea into a day-by-day route with a budget breakdown and a packing list. Handy when you would otherwise build the spreadsheet yourself. CX Codex +1 526installs kontour-travel-planner Bookingdesk-AI kontour-travel-planner turns an AI agent into a travel planner that walks through nine trip dimensions and builds a day-by-day itinerary. Useful when a trip has to be assembled from scattered wishes. CX Codex +1 481installs

From the same set29

The whole set →
checkpoint Saves named Git checkpoints during a Claude Code workflow and compares changed files, test results, and test coverage against earlier marks. CX Codex +1 ★ 6,739repo stars learn The learn slash command turns reusable lessons from the current session into skills. Run it after a difficult fix, debugging session, or project-specific discovery. CX Codex +1 ★ 6,739repo stars setup-pm setup-pm — a command to configure which package manager (npm, pnpm, yarn, or bun) Claude Code uses in your project or globally. Use it when you want to enforce a specific manager across your workflow. CX Codex +1 ★ 6,739repo stars code-reviewer The code-reviewer subagent reviews code changes for security vulnerabilities, bugs, performance problems, and style violations. Run it immediately after writing or modifying code to catch issues before they reach production. CX Codex ★ 6,739repo stars orchestrate orchestrate routes a complex task through a sequence of agents and combines their findings into a report. Choose a workflow for a feature, bug fix, refactor, or security review. CX Codex +1 ★ 6,739repo stars plan Command invokes a planner sub-agent that breaks down the task into phases, assesses risks, and waits for confirmation before touching any code. CX Codex +1 ★ 6,739repo stars architect An opus-powered subagent for designing scalable software architecture, analyzing technical trade-offs, and drafting Architecture Decision Records. CX Codex ★ 6,739repo stars tdd-guide The tdd-guide subagent guides feature work, bug fixes, and refactoring through a test-first workflow. It also checks test coverage against an 80% target. CX Codex ★ 6,739repo stars

More in the catalog

Project sponsors

Companies that keep this analytics open