Incremental Implementation

Problem

Multi-file changes and new features often fail when too much code is written at once: errors are harder to localize, tests fail late, and commits become noisy. SKILL.md focuses on avoiding one-shot feature implementation and instead advancing through verifiable increments.

How It Works

The skill frames implementation as small slices that keep the system working and testable:

• Implement: build the smallest complete piece of functionality instead of laying down large code first
• Test: run existing tests or add a test for the slice
• Verify: confirm build, tests, and manual checks pass
• Commit: save progress with a descriptive message
• Continue: carry the current state into the next slice without restarting

It favors vertical slices, such as one complete path through API, service, and UI, before expanding the scope.

Boundaries

Use it for multi-file changes, task-based feature work, refactoring, and especially when you are about to write more than roughly 100 lines before testing. For small single-file or single-function changes, skipping the process can be reasonable.