A planning command for breaking .NET work into small tasks with dependencies, acceptance criteria, and verification commands. It works from project files and an existing specification, which describes what the software should do.

Use it to create a reviewed plan in `tasks/plan.md` and a task list in `tasks/todo.md`, with checks such as `dotnet build`, filtered tests, and formatting verification.

Large changes are easier to implement when each step has a clear outcome and a way to check it. The plan also shows which tasks must come first, such as a database model before its migration or endpoint.

plan — Command for coding agents by peterblazejewicz: A planning command for breaking .NET work into small…

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/peterblazejewicz/claude-plugins/plan

Clone the repo

git clone --depth 1 https://github.com/peterblazejewicz/claude-plugins

Or install dotnet-skills, the plugin that ships this one along with the rest of its 24 skills, 9 commands, 4 agents.

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/peterblazejewicz/claude-plugins/plan.svg)](https://agentmods.dev/commands/peterblazejewicz/claude-plugins/plan)

Your own site

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

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

When invoked 381 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.00024	$0.00381
Opus 5	$0.00012	$0.00191
Sonnet 5	$0.00005	$0.00076
Haiku 4.5	$0.00002	$0.00038

Measured 3d ago against content hash 5cbd28d6c7b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

plugins/dotnet-skills/commands/plan.md · 24 lines

What it actually says

Invoke the dotnet-skills:planning-and-task-breakdown skill.

Read the existing spec (SPEC.md or equivalent) and the relevant parts of the solution — *.sln, Directory.Packages.props, global.json, affected .csproj files, and the projects they touch. Then:

Enter plan mode — read only, no code changes
Identify the dependency graph between projects and between the tasks themselves (e.g. EF Core model → migration → repository → endpoint → tests)
Slice work vertically (one complete path per task, not horizontal layers per project)
Write tasks with acceptance criteria and concrete verification steps — dotnet build -warnaserror, dotnet test --filter FullyQualifiedName~Xxx, dotnet format --verify-no-changes
Add checkpoints between phases
Present the plan for human review

Save the plan to tasks/plan.md and the task list to tasks/todo.md.

Source & Modifications

Upstream: addyosmani/agent-skills — .claude/commands/plan.md at pinned SHA 44dac80
Status: modified (skill reference retargeted to the dotnet-skills: prefix; codebase-reading list names .NET-specific artifacts *.sln / Directory.Packages.props / global.json / .csproj; dependency-graph example names an EF Core vertical slice; verification steps use dotnet build -warnaserror / dotnet test --filter / dotnet format --verify-no-changes)

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 · 24 lines · 24 tokens per session scan A 5cbd28d6c7b7

Subscribe to this mod's changes

plan is a command published in the GitHub repository peterblazejewicz/claude-plugins (7 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 381 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.

C# and .NET Languages Planning agentic-ai avalonia claude-code copilot developer-experience

plan

Getting it into your agent

Wrote this? Show the measurements

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

speckit.assess.intake

brownfield-map

security-review

pre-ship

rclone_copy

rclone_checksum