The top ten at a glance

12 Best Claude Code Prompts for Planning: the top prompts and what you get from each
PromptWhat you get
Claude Code Repo Recon and Implementation Plan for a New FeatureHas Claude Code inspect a repository read-only and produce an evidence-based implementation plan with file-level changes, tests, risks, and open questions. Use it to decide whether to start, split, or clarify a feature before any code is written.
Feature idea to spec and tickets: Multi-Step Agent Workflow for Claude Code, Codex or ChatGPTGrills a feature idea with recommended answers, pauses for you to confirm or correct them, writes a spec with numbered acceptance criteria, splits it into vertical-slice tickets in parallel, checks that every criterion is covered and every ticket is small and testable, and exports for your tracker.
Claude Code Plan-Then-Implement a Feature With Approval CheckpointsMakes Claude Code explore the repo, write a step-by-step plan for your approval, then build the feature in small verified steps, stopping at each checkpoint for your go-ahead.
Interview Me Then Plan: Requirements Interview Before Any CodeClaude Code questions you about a feature's requirements and edge cases, then delivers an implementation plan with acceptance criteria and test commands, without writing code first.
Claude Code Feature Implementation Plan and Build from a Ticket with Repo Convention DiscoveryHas Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Codebase Tour for a Specific TaskExplores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Grill The Plan: Agent Skill (SKILL.md) for Claude Code, Codex and CursorInterviews you about a plan one question at a time, with a recommended answer for each, until every design decision is resolved, then writes a decision log and a one-page plan.
Write An Implementation Plan: Agent Skill (SKILL.md) for Claude Code, Codex and CursorTurns an approved design or spec into an ordered plan another agent or developer can execute: small steps with files to touch, the test to write first, exact commands, done criteria, dependency order, parallel groups, risks and rollback.
Dependency Graph Planner for a Multi-Agent Software Release WorkflowTurns a list of release tasks into a dependency graph with parallel batches, critical path, shared-resource conflicts, and agent assignments. Supports the decision on what to run now versus wait on.
Parallel Git Worktree Task Split with Interface Contracts and Merge OrderTurns a pasted feature spec into independent coding-agent tasks with file ownership, interface contracts, a merge order and a done command for each task.

FAQ

About this list

The first prompts work read-only. The agent inspects how similar features are built, lists the files it would change and the tests it would add, and names the risks and open questions. Others interview you one question at a time until each decision is settled, then write the plan and acceptance criteria.

Further down are prompts for larger jobs: splitting a feature spec into tasks for parallel agents with file ownership and a merge order, a dependency graph for a release, and agent skills that turn a spec into a step-by-step plan. They pair well with plan mode in Claude Code, which stops the agent from editing until you agree.

Do I need plan mode to use these prompts?

No. The prompts that work inside a repository tell the agent to wait for your approval before it edits, and the rest only write a plan, so they work in a normal session too. Plan mode adds a hard stop on top of that, which is useful in a repository you don't know well. Switch it on before you paste, then approve the plan to let the agent continue.

How long should a good plan be?

Long enough to name every file that changes, the order of the steps, the test for each step and what done looks like. If the plan runs to many pages, the task is too big for one session; ask the agent to split it, and plan the first part properly before you start.

What if the plan is wrong?

Correct it in plain words before you approve, such as a file it missed or a library you don't want. The plan is cheap to change at this point and expensive to change after the code exists. The interview prompts help most here, because they ask about edge cases you might not think to mention.