# plan_new_feature

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.

- command · `type=command` · Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI · ★ 1573 repo stars
- Author: disler
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/disler/claude-code-hooks-multi-agent-observability/tree/HEAD/.claude/commands/bench/plan_new_feature.md
- Updated: 2026-02-08
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/plan-new-feature

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/plan_new_feature.md` — Call it with /plan_new_feature. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/plan_new_feature.md` — Call it with /prompts:plan_new_feature. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/plan_new_feature.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/plan_new_feature.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/disler/claude-code-hooks-multi-agent-observability/tree/HEAD/.claude/commands/bench/plan_new_feature.md

## When to use it
- break feature requirements into implementation steps
- record architecture decisions before coding
- define checks and completion criteria
- save a development plan under `specs/`

## Example prompts
- 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`.

## Similar
- [implement-plan-preflight](https://affpapa.org/en/nevibecode/skills/implement-plan-preflight.md) — skill · 125 installs
- [new-track](https://affpapa.org/en/nevibecode/commands/new-track.md) — command · ★ 42780 repo stars
- [swarm-plan](https://affpapa.org/en/nevibecode/skills/swarm-plan.md) — skill · ★ 539 repo stars
- [speckit.plan](https://affpapa.org/en/nevibecode/prompts/speckitplan.md) — prompt · ★ 110 repo stars
- [feature-forge](https://affpapa.org/en/nevibecode/skills/feature-forge.md) — skill · 4600 installs
- [feature-analyzer](https://affpapa.org/en/nevibecode/commands/feature-analyzer.md) — command · 158 installs

From the same set: [disler/claude-code-hooks-multi-agent-observability](https://affpapa.org/en/nevibecode/by/disler/claude-code-hooks-multi-agent-observability.md) — 20 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
