Skip to main content
command CX Codex

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

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/plan_new_feature.md
Open on GitHub

What 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.md

Call it with /plan_new_feature. For all projects use ~/.claude/commands/

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.

Similar slash commands

All slash commands for Writing and docs →

From the same set20

The whole set →
find_and_summarize find_and_summarize locates source files across target directories and creates concise two-sentence summaries in a YAML file. Useful for documenting modules without subagents. CX Codex +1 ★ 1,573repo stars create-worktree-subagent The create-worktree-subagent subagent creates isolated git worktrees for parallel development. Use it when the request explicitly delegates worktree creation to a subagent. CX Codex ★ 1,573repo stars docs-scraper docs-scraper — a subagent that fetches a documentation page by URL and saves it as a markdown file in ai_docs/. Handy when your agent needs a local copy of the docs. CX Codex ★ 1,573repo stars quick-plan quick-plan turns requirements into structured implementation blueprints stored in the specs/ folder. Useful before starting complex refactoring or new feature work. CX Codex +1 ★ 1,573repo stars load_ai_docs load_ai_docs — a command that downloads documentation from specified URLs and saves it as markdown files via model-specific subagents. Designed for documentation benchmarking and testing AI model capabilities. CX Codex +1 ★ 1,573repo stars t_metaprompt_workflow t_metaprompt_workflow generates structured Claude Code slash commands from a high-level task description while checking Anthropic docs. CX Codex +1 ★ 1,573repo stars scout-report-suggest-fast scout-report-suggest-fast hunts a described problem through a codebase and returns file paths, line numbers and a fix plan. It only reads. CX Codex ★ 1,573repo stars list_worktrees_prompt list_worktrees_prompt inspects git worktrees under the trees/ folder, detects active process ports, and outputs a runtime status report. CX Codex +1 ★ 1,573repo stars

Project sponsors

Companies that keep this analytics open