incremental-implementation

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

Updated May 21, 2026
One-click install
npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill incremental-implementation-nicorevo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: incremental-implementation
Source: https://github.com/nicorevo/AI-SDLC-Template/tree/main/.opencode/skills/incremental-implementation
Command: npx skills add https://github.com/nicorevo/AI-SDLC-Template --skill incremental-implementation-nicorevo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large features implemented in one pass produce unreviewable diffs, hidden bugs, and broken builds. This Skill enforces an increment cycle — implement, test, verify, commit — so every change lands in a working, testable state. ## Core Features & Use Cases - Vertical Slicing Strategies: Guides slicing by end-to-end functionality, API contracts, or risk-first ordering so each slice delivers working behavior. - Implementation Rules: Enforces simplicity-first design, scope discipline, compilable states, feature flags, safe defaults, and rollback-friendly commits. - Per-Increment Checklist: Verifies tests, build, type checking, and linting with the repository's own commands after every slice. - Use Case: When building a task management feature, implement create-task end to end (DB, API, UI), test and commit it, then add list, edit, and delete as separate verified slices instead of one large change. ## Quick Start Ask the agent to implement the next task from the plan incrementally, starting with only the database schema and API endpoint, running the repository's tests and build after each slice before committing.

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 projects?▼

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 working and testable, unlike horizontal layers that deliver nothing usable until the end.

When should I use feature flags for incomplete work?▼

Use feature flags when a feature is not ready for users but increments need to merge to the main branch. Gate the new code behind an environment variable or config flag so incomplete work stays hidden while small commits keep landing.

When is incremental implementation not needed?▼

Skip it for single-file, single-function changes where the scope is already minimal. The discipline targets multi-file changes, new features from task breakdowns, and any work exceeding roughly one hundred lines before testing.

Why should refactors be separate commits from features?▼

Mixing refactors with features makes both harder to review and debug, and complicates rollbacks. Separate commits keep each change doing one logical thing, so a bug can be traced and reverted independently.