A command for writing a structured implementation plan for a Symfony feature.

Use it to plan the work needed to build a new Symfony feature.

It helps break a feature into clear development steps before code changes begin.

write-plan — Command by dev-toolings

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/dev-toolings/superpowers-symfony/write-plan

Clone the repo

git clone --depth 1 https://github.com/dev-toolings/superpowers-symfony

Or install superpowers-symfony, the plugin that ships this one along with the rest of its 37 skills, 13 commands, 7 agents, 1 hook.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00009	$0.00029
Opus 5	$0.00005	$0.00015
Sonnet 5	$0.00002	$0.00006
Haiku 4.5	$0.00001	$0.00003

Measured 3d ago against content hash 67493e68699c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

write-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 3d 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.

commands/write-plan.md · 6 lines

What it actually says

Use the symfony:writing-plans skill exactly as written.

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.

3d ago First seen · 6 lines · 9 tokens per session scan A 67493e68699c

Subscribe to this mod's changes

write-plan is a command published in the GitHub repository dev-toolings/superpowers-symfony (206 stars, last pushed 27d ago), licensed MIT. It adds 9 tokens to every session and 29 once invoked, about $0.0000 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-30.

Planning ai-agents anthropic api-platform claude-code claude-code-plugin cqrs

write-plan

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

spec

spec-status

add-business-rule

api-resource-ship

self-audit-api

test