planning — Claude Code prompt: plan and install
planning is a Claude Code prompt that inspects a repository, maps requirements to acceptance criteria, and sets verification steps before coding.
no license ★ 336 updated 2026-11-14
.claude/commands/planning.mdWhat planning does
The planning prompt asks the coding agent to inspect the project before changing it and identify the files that may be created or edited. It turns each requirement into a concrete task with an acceptance check, then covers edge cases, failures, race conditions, security risks, and regressions.
The verification section chooses tests when the project already has test tooling, or exact manual steps and CLI commands otherwise. The plan stops before implementation and waits for approval. Adding test dependencies requires a separate request.
What it helps with
- inspect a repository before changing code
- turn requirements into tasks and acceptance checks
- review edge cases, failures, races, and security risks
- define automated or manual result verification
Example prompts for the agent
- Run
/planningbefore making changes in the repository. - Create an implementation plan for this task with target files, acceptance checks, and verification steps.
- Review the risks before implementation and wait for my approval of the plan.
How to install planning
Manually: put the files in place
.claude/commands/planning.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about planning
How do I install planning in Claude Code?
Place the prompt file at .claude/commands/planning.md.
What does planning do?
It examines the repository, connects requirements with concrete tasks and acceptance checks, then describes risks and result verification before implementation begins.
How does planning verify the result?
It uses automated tests when the project has test tooling. Otherwise, it defines exact manual reproduction steps or CLI commands.