Agent skill · software engineering · sickn33
incremental-implementation
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Why this skill is useful
Codifies a structured approach to incremental implementation that the AI could infer but now doesn't have to guess.
What it needs
About 7k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
Supporting material availability This catalog copy contains the inline guidance below, but does not include the following supporting paths. They are external prerequisites, not bundled files: <support-root>/references/definition-of-done.md Obtain the required material from the declared upstream source, or from a user-provided installation of that source. Resolve each path relative to that installation, inspect its contents, and verify any applicable license and execution prerequisites. Do not run a command or claim a referenced procedure was followed until its required file exists. Do not fabricate the missing scripts or treat an unrelated file with the same name as equivalent. Independent steps fully documented here can proceed within the user’s authorized scope; report any dependent step as unavailable. 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-function changes where the scope is already minimal. The Increment Cycle For each slice: 1. Implement the smallest complete piece of functionality 2. Test — run the test suite (or write a test if none exists) 3. Verify — confirm the slice works as expected (tests pass, build succeeds, 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: Each slice delivers working end-to-end functionality. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/incremental-implementation