skills.rest
assafmanor
assafmanorCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

incremental-implementation

Implements multi-file code changes in thin vertical slices with per-slice testing and commits.

Updated Jul 9, 2026
Search Tags:#testing#refactoring#code implementation#feature flags#incremental development#atomic commits#vertical slices
One-click install
npx skills add https://github.com/assafmanor/waypoint --skill incremental-implementation-assafmanor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incremental-implementation
Source: https://github.com/assafmanor/waypoint/tree/main/.claude/skills/incremental-implementation
Command: npx skills add https://github.com/assafmanor/waypoint --skill incremental-implementation-assafmanor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features and multi-file changes often get written in one giant pass, making bugs hard to locate, reviews painful, and rollbacks risky. This Skill enforces an incremental delivery discipline so every change lands in small, tested, independently revertable steps. ## Core Features & Use Cases - Increment Cycle: A repeatable Implement → Test → Verify → Commit loop that keeps the codebase buildable and green after every slice. - Slicing Strategies: Vertical slices, contract-first slicing for parallel backend/frontend work, and risk-first slicing to de-risk uncertain components early. - Implementation Rules: Simplicity-first checks, scope discipline, feature flags for incomplete work, safe defaults, and rollback-friendly commits. - Use Case: When adding a full CRUD feature, deliver it as four slices (create, list, edit, delete), each tested end-to-end and committed separately, instead of one 500-line change. ## Quick Start Ask the agent to implement the next task incrementally, starting with only the database schema and API endpoint, running the test and build commands after each slice before moving to the UI.

Frequently Asked Questions about incremental-implementation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a large feature incrementally?▼

Break the feature into thin vertical slices where each slice delivers working end-to-end functionality. For each slice, implement the smallest complete piece, run the test suite, verify the build, commit with a descriptive message, then move to the next slice.

What is vertical slice development in software engineering?▼

Vertical slicing builds one complete path through the stack per increment, such as database plus API plus UI for a single operation. Each slice leaves the system in a working, testable state instead of completing one layer at a time.

When should I not use incremental implementation?▼

Skip it for single-file, single-function changes where the scope is already minimal. The overhead of slicing and per-increment verification adds no value when the entire change is small and atomic.

How do feature flags help merge incomplete features?▼

Feature flags let you merge small increments to the main branch without exposing unfinished work to users. Gate the new code behind an environment variable that defaults to off, then enable it when the feature is complete.

Why should each commit contain only one logical change?▼

Mixing a feature, a refactor, and a config update in one commit makes bugs harder to locate and rollbacks painful. Separate commits keep each change reviewable, independently revertable, and easier to debug when something breaks.

Related Skills

Explore More Software Engineering Skills→
aaaa47080aaaa47080
4

writing-plans

Draft implementation-ready plans with tasks, tests, and milestones from a spec.

Community
Intermediate
tale-projecttale-project
20

ship

Gate code changes through Definition of Done, reviews, and automated tests before opening a PR.

Official
Advanced
nntoannntoan

test-driven-development

Guides test-first development using the RED-GREEN-REFACTOR cycle across any language or test framework.

Community
Intermediate
Bbar0n234Bbar0n234
35

aidd-methodology

Document architecture, contracts, and constraints before coding in AI-driven projects.

Community
Advanced