القائمة
Ship working vertical slices instead of big-bang implementations
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Build UIs that work for all users including keyboard navigation, screen readers, and WCAG 2.2
Design multi-agent systems with robust tool interfaces, state management, and failure handling
Build ML systems with disciplined training, evaluation, deployment, and safety practices
Design APIs that are stable, ergonomic, and evolvable
Design systems at the right scale with explicit trade-off documentation
Design services that are reliable, observable, secure, and maintainable
| name | incremental-implementation |
| description | Ship working vertical slices instead of big-bang implementations |
| difficulty | senior |
| domains | ["general"] |
Incremental implementation is the practice of delivering working software in the smallest useful increments. Each increment is deployable, testable, and provides value or learning. The goal is to eliminate the "everything works or nothing works" state that characterizes big-bang development.
Ask: what is the smallest version of this feature that proves the core hypothesis or delivers the core value? That is your first increment.
A vertical slice cuts through all layers: UI → API → service → database → response. Implement all layers for the minimal slice before moving to the next feature.
Implement the thinnest possible end-to-end version: returns hardcoded data, has no error handling, no edge cases. Make it work end-to-end first.
Write tests that cover the happy path of the walking skeleton. These tests will protect you as you add flesh to the skeleton.
Add real data, error handling, and edge cases incrementally. Run tests after each addition.
Every commit should leave the system in a deployable state. Use feature flags if necessary to hide incomplete work from end users.
Don't accumulate increments. Ship each one. Unreleased code is risk, not progress.
"I need to build the whole thing before I can test it" This is the wrong architecture. If you can't test a slice without the whole system, redesign so you can.
"It's faster to build it all at once" It is faster to write code all at once. It is not faster to debug, review, and deploy code all at once.
"Feature flags add complexity" Less complexity than a multi-week branch merge. Feature flags are incremental delivery infrastructure.
