plan_new_feature — Claude Code command: planning and install
plan_new_feature is a Claude Code command that turns a feature request into a development plan saved under specs/. It maps the work before coding starts.
no license ★ 1,573 updated 2026-02-08
.claude/commands/plan_new_feature.mdWhat plan_new_feature does
The command reviews the requested change, chooses a technical direction, and writes a development blueprint. The document covers goals, architecture choices, implementation steps, possible obstacles, testing, and completion criteria. Its filename follows plan_new_feature_<RUN_NAME>.md.
The plan goes into specs/, and the command reports the file and its main sections when finished. It does not implement the feature or delegate work to subagents, so coding happens separately.
What it helps with
- break feature requirements into implementation steps
- record architecture decisions before coding
- define checks and completion criteria
- save a development plan under
specs/
Example prompts for the agent
- Draft an implementation plan for these requirements and save it as
payments. - Review this feature request, outline the build and test steps, and name the plan
search. - Write a specification with architecture choices and completion criteria under the name
dashboard.
How to install plan_new_feature
Manually: put the files in place
.claude/commands/plan_new_feature.mdCall it with /plan_new_feature. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/plan_new_feature.mdCall it with /prompts:plan_new_feature. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/plan_new_feature.prompt.mdManually: put the files in place
.gemini/commands/plan_new_feature.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about plan_new_feature
How do I install plan_new_feature in Claude Code?
Copy the command file to .claude/commands/plan_new_feature.md.
What does plan_new_feature do?
It analyzes a request and writes a development plan to specs/plan_new_feature_<RUN_NAME>.md, covering the technical approach, implementation, and testing.
Does the command implement the feature?
No. It produces a plan; development must be done separately.