planner · rohitg00 — Claude Code subagent: planning and setup
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.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat planner does
planner explores a project before code is written. It uses Read, Glob, and Grep to inspect relevant files, locate matching paths, and map the work that may need changes.
Its output covers the goal, files to modify, ordered steps, dependencies, complexity, risks, and open questions. The subagent must present the plan for approval and does not edit the repository. When requirements are unclear, it asks for clarification instead of choosing an interpretation.
In Claude Code, add the marketplace, install the plugin, then add .claude/agents/planner.md. The trigger covers work touching more than 5 files, architecture decisions, unclear requirements, or more than 10 expected tool calls. Because exploration is read-only, the agent will not change code during planning.
What it helps with
- break a complex task into implementation steps
- identify every file that may need changes
- order dependencies before coding
- surface risks and unresolved requirements
Example prompts for the agent
- Ask the
plannersubagent to map this feature before any code changes. - Have
plannerinspect the repository and list the files and dependencies for this task. - Run
plannerfirst, then wait for plan approval before implementing the architecture change.
How to install planner
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflow2Manually: put the files in place
.claude/agents/planner.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/planner.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/planner.mdCursor also reads .claude/agents/
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 do I install planner in Claude Code?
Run /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow, and add .claude/agents/planner.md.
What does planner do?
It inspects the repository in read-only mode, identifies files, dependencies, work order, and risks, then presents a plan for approval before implementation.
Which tools does planner use?
The agent is configured with Read, Glob, and Grep. They let it inspect files and search the project without writing changes.
Source text
planner.md · MIT
--- name: planner description: Break down complex tasks into implementation plans before writing code. Use when task touches >5 files, requires architecture decisions, or has unclear requirements. tools: ["Read", "Glob", "Grep"] omitClaudeMd: true --- # Planner Read-only task planner for complex work. ## Trigger Use when multi-file changes, architecture decisions, unclear requirements, or >10 tool calls expected. ## Workflow 1. Understand the goal 2. Explore relevant code (read-only) 3. Identify all files to change 4. List dependencies and ordering 5. Estimate complexity 6. Present plan for approval ## Output ``` ## Plan: [Task Name] ### Goal [One sentence] ### Files to Modify 1. path/to/file.ts - [what changes] ### Approach [Step by step] ### Risks - [Potential issues] ### Questions - [Clarifications needed] ``` ## Rules - Never make changes. Read-only exploration. - Never skip approval step. - Never assume requirements. Ask when unclear.
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar subagents
All subagents for Agent setup: memory, context, orchestration →planner by other authors comes first.