What problem does it solve? Large features and multi-file changes often get written in one giant pass, leaving bugs hidden among hundreds of lines and the codebase broken between edits. This Skill enforces an implement-test-verify-commit cycle so every change lands as a small, working, revertable increment. ## Core Features & Use Cases - Thin Vertical Slicing: Breaks features into end-to-end slices (e.g., create, list, edit, delete) where each slice leaves the system working and testable. - Slicing Strategies: Provides contract-first slicing for parallel backend/frontend work and risk-first slicing to prove uncertain pieces early. - Scope and Simplicity Discipline: Enforces 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 the database schema and API endpoint first, run the test suite, commit, then add the UI in the next increment instead of writing everything at once. ## Quick Start Implement the next task from my plan incrementally, starting with just the backend slice, and run the test and build commands after each step.
