incremental-implementation

incremental-implementation is a skill for Claude Code from peterblazejewicz/claude-plugins. It costs 71 tokens per session (3,221 once invoked), scanned A, original, MIT.

A step-by-step method for making .NET and C# changes in small, working pieces. After each piece, the project is built and its tests are run before continuing.

In plain words
What is it for?
Use it for features, refactors, or other changes spanning multiple files, projects, or assemblies—the compiled units that make up a .NET solution.
Why use it?
Large changes are harder to debug when everything is written at once. Small verified steps make failures easier to find and keep the code working throughout the change.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dotnet-skills plugin — 24 skills, 9 commands, 4 agents shipped together

Good fit Use it for features, refactors, or other changes spanning multiple files, projects, or assemblies—the compiled units that make up a .NET solution.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/peterblazejewicz/claude-plugins/incremental-implementation
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.

Any agent
npx skills add peterblazejewicz/claude-plugins --skill incremental-implementation
Clone the repo
git clone --depth 1 https://github.com/peterblazejewicz/claude-plugins

Made for: Claude Code.

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.

agentmods badge for incremental-implementation

README.md
[![agentmods](https://agentmods.dev/badge/skills/peterblazejewicz/claude-plugins/incremental-implementation/github.svg)](https://agentmods.dev/skills/peterblazejewicz/claude-plugins/incremental-implementation)
Your own site
<a href="https://agentmods.dev/skills/peterblazejewicz/claude-plugins/incremental-implementation"><img src="https://agentmods.dev/badge/skills/peterblazejewicz/claude-plugins/incremental-implementation/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.

agentmods 80×15 button for incremental-implementation

Your own site · 80×15
<a href="https://agentmods.dev/skills/peterblazejewicz/claude-plugins/incremental-implementation"><img src="https://agentmods.dev/badge/skills/peterblazejewicz/claude-plugins/incremental-implementation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,221 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.03221
Opus 5.5 $0.00028 $0.01288
Sonnet 5.5 $0.00014 $0.00644
Haiku 4.5 $0.00007 $0.00322

Measured 1mo ago against content hash e9ee7b0af5fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

incremental-implementation 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 1mo 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/skills/incremental-implementation/SKILL.md · 292 lines

How it starts

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

Incremental Implementation

Overview

Build in thin vertical slices — implement one piece, test it, verify it, then expand. Avoid implementing an entire feature in one pass. Each increment should leave the system in a working, testable state. This is the execution discipline that makes large features manageable.

When to Use

  • Implementing any multi-file change
  • Building a new feature from a task breakdown
  • Refactoring existing code
  • Any time you're tempted to write more than ~100 lines before testing

When NOT to use: Single-file, single-method changes where the scope is already minimal.

The Increment Cycle

┌──────────────────────────────────────┐
│                                      │
│   Implement ──→ Test ──→ Verify ──┐  │
│       ▲                           │  │
│       └───── Commit ◄─────────────┘  │
│              │                       │
│              ▼                       │
│          Next slice                  │
│                                      │
└──────────────────────────────────────┘

For each slice:

  1. Implement the smallest complete piece of functionality
  2. Test — run dotnet test (or write a test if none exists)
  3. Verify — confirm the slice works as expected (tests pass, dotnet build -warnaserror is clean, manual check)
  4. Commit -- save your progress with a descriptive message (see git-workflow-and-versioning for atomic commit guidance)
  5. Move to the next slice — carry forward, don't restart

Slicing Strategies

Vertical Slices (Preferred)

Build one complete path through the stack:

Slice 1: Create a task (EF Core entity + migration + endpoint + basic view)
    → dotnet test passes, user can create a task via the UI

Slice 2: List tasks (query + endpoint + list view with bindings)
    → dotnet test passes, user can see their tasks

Slice 3: Edit a task (update command + endpoint + edit view)
    → dotnet test passes, user can modify tasks

Slice 4: Delete a task (delete command + endpoint + UI + confirmation)
    → dotnet test passes, full CRUD complete

Read the full file on GitHub · 292 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.

  1. 1mo ago First seen · 292 lines · 71 tokens per session scan A e9ee7b0af5fd

Subscribe to this mod's changes

incremental-implementation is a skill published in the GitHub repository peterblazejewicz/claude-plugins (8 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 3,221 once invoked, about $0.0003 per session on Opus 5.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.

Related

Other skills, from other repositories

build-and-test

How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.

microsoft/agent-framework · 26 tokens

verify-dotnet-samples

How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.

microsoft/agent-framework · 40 tokens

agents-sdk-dotnet-activityhandler-migration

Use when migrating a Microsoft 365 Agents SDK agent that uses ActivityHandler or TeamsActivityHandler to AgentApplication. This is ONLY for DotNet projects that uses Microsoft.Agents. packages. Triggered by Agents SDK bots that subclass ActivityHandler or TeamsActivityHandler that need to be modernized to…

microsoft/Agents · 76 tokens

teams-sdk-to-agents-sdk-dotnet-migration

Use when migrating a customer's Teams SDK (teams.net) bot to the Microsoft 365 Agents SDK in .NET. Triggered by projects that depend on Microsoft.Teams.Plugins.AspNetCore, Microsoft.Teams.Apps, or Microsoft.Teams.Api and call builder.AddTeams() / app.UseTeams().

microsoft/Agents · 72 tokens

agents-sdk-dotnet

Use when any code imports Microsoft.Agents.Hosting.AspNetCore, Microsoft.Agents.Builder, or related Agents SDK packages, or when the user is building, configuring, or asking questions about a Microsoft 365 Agents SDK agent in C# / .NET. Trigger on questions about appsettings.json, connection configuration…

microsoft/Agents · 112 tokens

bf-to-agents-sdk-dotnet-migration

Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.

microsoft/Agents · 56 tokens