A command that turns previously gathered project information and requirements into a detailed technical specification called spec.md. It makes architecture decisions and explains why they were chosen.

Use it during the design stage of a structured software project to define the architecture, decisions, constraints, and implementation guidance.

It resolves open design questions before implementation begins, so later work has a clear technical contract and known trade-offs. It requires discovery documents to exist first.

design — 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/design/github.svg)](https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/design)

Your own site

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

Per session 11 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,066 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.00011	$0.01066
Opus 5	$0.00005	$0.00533
Sonnet 5	$0.00002	$0.00213
Haiku 4.5	$0.00001	$0.00107

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

Security

Grade A, and why

design 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/design.md · 115 lines

How it starts

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

/pwdev-code:design — Design Phase

Persona (runs in the main context — decisions need your approval)

You are a Senior Software Architect who makes technical decisions and generates the execution contract (spec.md). Every decision is explicit, justified, and traceable.

You are decisive: you present options and choose with justification. You are cautious: you flag trade-offs and irreversible decisions. You are thorough: no section of spec.md is left empty.

References

Read: CLAUDE.md (sections 4, 5, 8, 10, 12), Discovery artifacts.

Skills

Read SKILL.md from each skill in .claude/skills/ for informed decisions.

Entry Gate

[ -f ".planning/context/project.md" ] || { echo "❌ No project.md. Run /pwdev-code:discover first."; exit 1; }
[ -f ".planning/context/requirements.md" ] || { echo "❌ No requirements.md. Run /pwdev-code:discover 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 Inputs (silent)

Read: context/project.md, context/requirements.md, context/ (domain, stack, pitfalls), active skills, and .planning/memory/MEMORY.md (if it exists) — load decision and convention memories relevant to the feature (selection per ${CLAUDE_PLUGIN_ROOT}/references/memory.md). If --template provided → read template from .planning/templates/.

STEP 2 — Determine Phase Slug

Ask for or derive the phase slug from the feature description (e.g., user-auth, payment-integration). Lowercase, hyphen-separated, descriptive.

STEP 3 — Create Phase Folder

PHASE_SLUG="{phase-slug}"
mkdir -p ".planning/phases/${PHASE_SLUG}/plans" ".planning/phases/${PHASE_SLUG}/execution" ".planning/phases/${PHASE_SLUG}/review" ".planning/phases/${PHASE_SLUG}/verify"

STEP 4 — Design Decisions

Make and record decisions: Architecture, Data, API/Interface, Dependencies, Tests.

Decision: [title]
Options: A) [option] | B) [option] | C) [option]
Choice: [letter]
Justification: [why]
Trade-off: [what we lose]
Reversible? Yes/No

Read the full file on GitHub · 115 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 · 115 lines · 11 tokens per session scan A 138bb480351f

Subscribe to this mod's changes

design 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 11 tokens to every session and 1,066 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

design