Incremental Implementation

Overview

Build one coherent slice at a time. Keep the tree understandable and verifiable after each step.

When to Use

• Any implementation spanning multiple files
• Refactors that can be split into behavior-preserving steps
• Changes with meaningful rollback boundaries

Process

1. Pick the next smallest slice that produces visible progress.
2. Load only the context needed for that slice.
3. Make the scoped code or docs change.
4. Run the narrowest relevant verification immediately.
5. Expand only when the previous slice is coherent and proven.

Rationalizations

Red Flags

• A single diff mixes feature work, cleanup, and infrastructure drift
• Verification is postponed until the end
• The next change depends on unproven assumptions

Verification

• Each slice has a clear purpose
• Relevant checks run before moving on
• Scope stayed narrow
• The tree remains coherent after each step