# plan_w_team

The plan_w_team command turns requirements into an engineering plan and saves it under specs/. Use it when a task needs steps, ownership, and acceptance criteria before coding.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 3990 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-mastery/tree/HEAD/.claude/commands/plan_w_team.md
- Updated: 2026-03-04
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/plan-w-team

## What it does

\`plan_w_team` takes a user request plus an optional instruction for arranging the team. It classifies the task, assesses its complexity, reads the codebase directly, and writes a plan to `specs/<plan-name>.md`. The document covers the task, objective, relevant files, ordered work items, acceptance criteria, and team members.

The command is planning-only: it does not implement code or deploy agents. Its orchestration flow can create shared tasks, assign owners, add blockers, resume an agent, and run independent work in parallel through Claude Code tools. Stop hooks then inspect the new Markdown file in `specs/` and check for required sections.

Validation calls `uv run` with scripts under `.claude/hooks/validators/`, so the environment needs `uv` available for those checks to complete. The command uses the `opus` model.

## Install

### Claude Code (native platform)

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

### Codex

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

### GitHub Copilot

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

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/plan_w_team.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-mastery/tree/HEAD/.claude/commands/plan_w_team.md

## When to use it
- turn requirements into an implementation plan
- split team work into dependent tasks
- record acceptance criteria in Markdown
- assign owners across a planned workflow
- validate the structure of a saved plan

## Example prompts
- Create an implementation plan for adding authentication and save it under `specs/`.
- Break this feature into team tasks, assign owners, and show which tasks depend on earlier work.
- Plan the refactor only. Do not write code, and save the result in `specs/`.

## Similar
- [goal-plan](https://affpapa.org/en/nevibecode/skills/goal-plan.md) — skill · 771 installs
- [implement_plan](https://affpapa.org/en/nevibecode/skills/implement-plan.md) — skill · 502 installs
- [plan-execution](https://affpapa.org/en/nevibecode/commands/plan-execution.md) — command · ★ 112 repo stars
- [plan-plays](https://affpapa.org/en/nevibecode/commands/plan-plays.md) — command · ★ 450 repo stars
- [speckit-plan](https://affpapa.org/en/nevibecode/skills/speckit-plan.md) — skill · 2600 installs
- [plan-interview](https://affpapa.org/en/nevibecode/skills/secondsky-plan-interview.md) — skill · 413 installs

From the same set: [disler/claude-code-hooks-mastery](https://affpapa.org/en/nevibecode/by/disler/claude-code-hooks-mastery.md) — 25 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
