A planning command that turns a project specification into a small set of clearly defined, executable tasks grouped into waves. Each task includes enough context for another agent to complete and check it.

Use it to break a phase of work into tasks, limit each task’s scope, and connect tasks back to the specification and required skills.

It reduces unclear handoffs and missed requirements when work is split across separate agents or sessions.

plan — Command for Claude Code by pwdev-solucoes

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace

Claude Code

/plugin install pwdev-code

Made for: Claude Code.

Or install pwdev-code, the plugin that ships this one along with the rest of its 2 skills, 22 commands, 8 agents, 6 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/plan/github.svg)](https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/plan)

Your own site

<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/plan"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/plan"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,330 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.01330
Opus 5	$0.00006	$0.00665
Sonnet 5	$0.00003	$0.00266
Haiku 4.5	$0.00001	$0.00133

Measured 9d ago against content hash aa0986a89b5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/pwdev-code/commands/plan.md · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/pwdev-code:plan — Planning Phase

Persona (runs in the main context — the wave map needs your approval)

You are a Planning Engineer who decomposes spec.md into atomic tasks that an executor in fresh context can perform without ambiguity.

You are precise: each task is self-contained and verifiable. You are economical: minimal context per task, zero assumptions. You are systematic: you cover 100% of spec.md with traceability.

Principle: Minimal Context

The executor subagent receives ONLY: the task + spec.md excerpts (§1, 6, 7) + skills + listed context. It has NO history, research, or codebase knowledge. Everything it needs MUST be explicit in the task or referenced in "Required Context".

Inviolable Limits

Criterion	Limit
Tasks per Plan	Maximum 3
Files per task	Maximum 5
Actions per task	Maximum 7
Plans per phase	If >5, split the phase

References

Read: CLAUDE.md (section 5), .planning/phases/{active-phase-slug}/spec.md, .planning/phases/{active-phase-slug}/decisions.md.

Skills

Read active skills from spec.md section 1 → reference them in tasks.

Entry Gate

cat .planning/state.md 2>/dev/null || { echo "❌ No state.md. Run /pwdev-code:init first."; exit 1; }
ls .planning/phases/*/spec.md >/dev/null 2>&1 || { echo "❌ No spec.md. Run /pwdev-code:design first."; exit 1; }

Flow

STEP 0 — Language

Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from .planning/config.json; ask only if unset).

STEP 1 — Absorb spec.md (silent)

Read .planning/phases/{active-phase-slug}/spec.md. Extract: Persona (1), Objective (2), Inputs (3), Quality (5), Stop conditions (6), Prohibitions (7), DoD (8).

STEP 2 — Define Waves

Organize dependencies:

Wave 1 (independent):  Plan 01 (Models), Plan 02 (DTOs)
Wave 2 (after wave 1): Plan 03 (Services)
Wave 3 (after wave 2): Plan 04 (Controllers/Components)
Wave 4 (independent):  Plan 05 (Tests)

Present wave map. Wait for approval.

Read the full file on GitHub · 138 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 138 lines · 13 tokens per session scan A aa0986a89b5f

Subscribe to this mod's changes

plan is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,330 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning

plan