What problem does it solve? Large features implemented in one pass produce untested, hard-to-review code where a single bug hides among hundreds of changed lines. This Skill enforces a disciplined increment cycle — implement, test, verify, commit — so every slice leaves the codebase in a working, testable state. ## Core Features & Use Cases - Increment Cycle: Each slice is implemented, tested against the suite, verified via build and type checks, then committed before moving on. - Slicing Strategies: Choose vertical slices (end-to-end paths through DB, API, and UI), contract-first slicing for parallel backend/frontend work, or risk-first slicing to prove the riskiest piece early. - Implementation Rules: Enforces simplicity-first design, scope discipline, one logical change per commit, feature flags for incomplete work, safe defaults, and rollback-friendly changes. - Use Case: When building a task management feature, implement create-task (DB + API + UI) as slice one with passing tests, then list, edit, and delete as separate committed slices instead of one large CRUD dump. ## Quick Start Ask the agent to implement the feature incrementally, starting with just the database schema and API endpoint, running tests and build after each slice before touching the UI.
