incremental implementation

Large pull requests are where bugs hide and reviews go to die. When an agent attempts to implement a complex feature in a single massive wall of code, it inevitably breaks existing functionality or misses edge cases. This skill enforces execution discipline by breaking down multi-file changes into thin, vertical slices that maintain a working system at every step.

What it does

• Vertical slicing ensures each increment delivers end-to-end functionality across DB, API, and UI.
• Scope discipline prevents "while I'm here" refactoring and unnecessary changes to adjacent files.
• Simplicity enforcement rejects premature abstractions and complex patterns in favor of naive, correct code.
• Continuous verification mandates running build and test commands after every logical change.
• Risk mitigation prioritizes high-uncertainty components first to fail fast.

How it works

1. Slice the task into the smallest complete pieces of functionality that leave the system in a testable state.
2. Implement the first slice using the simplest possible logic, avoiding any unrelated code cleanup.
3. Verify the change by running the repository's test suite, build commands, and type checkers.
4. Commit the verified slice with a descriptive message before moving to the next requirement.

Frameworks & tools

This skill is language-agnostic and works with any stack including Node.js, Python, Java, and Go. It integrates with standard development workflows using Git, CI/CD pipelines, and feature flagging systems.

Why this beats prompting it yourself

Generic prompts often lead agents to over-engineer solutions or produce massive diffs that are impossible to debug. This skill embeds strict rules against scope creep and premature abstraction, forcing the agent to prove correctness through code execution rather than just text generation.

Use cases

• Feature development from a complex task breakdown or technical specification.
• Refactoring legacy codebases where changes must be isolated to prevent regression.
• Parallel development using contract-first slicing for backend and frontend sync.
• Risk management for proof-of-concept work involving unstable third-party APIs or WebSockets.

Known limitations

Not recommended for single-file, single-function changes where the scope is already minimal. It requires an existing test or build command to provide meaningful verification.