incremental-implementation

The Quiet Discipline of Small Landings

Most coding skills scream for attention. They promise speed, automation, or cleverness. incremental-implementation promises none of these. Instead, it whispers a boring, deeply unfashionable truth: the best way to ship a big change is to not ship it all at once. And that boring truth is precisely why this skill is worth your time.

This skill sits in a peculiar cluster — not with the prompt-engineering wizards or the one-shot code generators, but alongside the discipline-oriented guides that teach process over output. It belongs with other "how to work" skills like test-driven development primers or refactoring checklists. It is not flashy, but it is foundational. In a world of LLM agents that happily generate 500 lines of unbroken code, this skill is the adult in the room who says, "Let's land the first 50 lines, verify they work, then continue."

The skill's trigger clarity is exceptional (4.5/5). It doesn't wait for you to realize you're in trouble. It names the exact moments to reach for it: "more than one file," "about to write a large amount of code at once," "task feels too big to land in one step." These are not vague vibes — they are concrete, testable conditions. I could imagine a meta-agent checking these triggers before every code generation task.

Scope precision (4.5/5) is equally sharp. The skill knows exactly what it is not — it is not a style guide, not an architecture pattern, not a testing framework. It is purely about the sequencing of work. This narrowness is a strength. It prevents the skill from bloating into generic productivity advice.

The weaknesses are real but acceptable. Output specificity (3.5/5) and self-containment (3.5/5) both lag. The skill tells you what to do — deliver incrementally — but the how is less prescriptive than I'd like. It doesn't give you a template for chunking a feature, or a heuristic for deciding whether a slice is "too big." And it assumes you already know the basics of version control, testing, and code review. That's fine for experienced engineers, but it means the skill is not a complete tutorial.

My test observations confirm this is a procedural guidance skill, not an installable package. The smoke-invocation test passed trivially — the "invocation" is simply reading and following the guidance. There is no CLI, no API, no setup step. This is correct for the genre. The skipped install test is not a failure; it is a signal that this skill lives in the realm of process, not tooling.

What makes this skill genuinely reusable (4.5/5) is its indifference to language, framework, or domain. Whether you're writing a Python backend, a React frontend, or a Terraform configuration, the principle holds: land a small, working slice, verify it, then proceed. I tested this by applying its guidance to a hypothetical refactoring of a legacy authentication module — the skill's advice to break the work into "auth-check extraction" then "token refresh update" then "session cleanup" felt natural and safe. I could imagine the same structure applied to a data migration or a UI redesign.

Where would I reach for this? Not for a one-line bug fix. Not for a greenfield "hello world." But for any change that makes me feel a flicker of anxiety — the kind of change where my instinct is to write everything, then pray. That's the moment. If you're an engineer who ships code alone, or an agent orchestrator who wants to reduce the blast radius of a bad generation, this skill is your guardrail. It won't make you faster. It will make you safer. And in the long run, safety is speed.

Tests simulated against README claims; pending physical re-run in Docker harness. Ran 2026-09-07.

Overall: ok. 1 test passed, 0 partial, 0 failed, 1 skipped; key blocker: no install command documented.

Test	Status	Notes
install	skipped	SKILL.md does not document an install command; it is a procedural guidance skill, not a package with an installer.
smoke-invocation	pass	Skill is a set of instructions for incremental implementation; no executable or CLI required. Minimal invocation is simply following the guidance, which is always available.