# incremental-feature-build

The incremental-feature-build command breaks a request into testable features, tracks progress in project files, and works through features one at a time. Use it for multi-stage implementation tasks.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/dev/incremental-feature-build.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/incremental-feature-build

## What it does

The command creates `.feature-tracking` with a feature list in `features.json` and a work log in `PROGRESS.md`. Claude Code expands the request into discrete items with priorities, dependencies, and verification steps. The schema covers areas such as functionality, UI, integrations, security, and accessibility.

For each item, Claude Code checks its dependencies, implements the feature, verifies it, and records a Git commit. It then updates the tracking files with the result. Work proceeds one feature at a time, with a commit after each one, so a long task produces a sequence of smaller changes in Git history.

## Install

### Claude Code (native platform)

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

### Codex

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

### GitHub Copilot

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

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/incremental-feature-build.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/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/dev/incremental-feature-build.md

## When to use it
- split a large request into testable features
- record dependencies between implementation steps
- track completed and pending work
- check edge cases and failure paths
- save implementation progress in Git commits

## Example prompts
- Break the account settings page into features and build them in sequence: `/dev:incremental-feature-build account settings page`.
- Add product search, including empty results and error handling: `/dev:incremental-feature-build product search`.
- Track an API migration as separate features and update progress after each: `/dev:incremental-feature-build API migration`.

## Similar
- [feature-tracking](https://affpapa.org/en/nevibecode/skills/feature-tracking.md) — skill · ★ 106 repo stars
- [incremental-build](https://affpapa.org/en/nevibecode/skills/incremental-build.md) — skill · 4500 installs
- [incremental-implementation](https://affpapa.org/en/nevibecode/skills/incremental-implementation.md) — skill · 77900 installs
- [team-feature](https://affpapa.org/en/nevibecode/commands/team-feature.md) — command · ★ 42780 repo stars
- [build](https://affpapa.org/en/nevibecode/skills/build.md) — skill · 2700 installs
- [vibe-build](https://affpapa.org/en/nevibecode/skills/vibe-build.md) — skill · ★ 3267 repo stars

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 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
