Build Software in Small, Verifiable Increments
Large changes are difficult to test, review, and recover when problems appear late. This skill breaks work into complete increments with explicit tests, verification, and rollback points.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "incremental-implementation" from https://skillstore.io/skills/addyosmani-incremental-implementation.md and its manifest at https://skillstore.io/api/skills/addyosmani-incremental-implementation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "incremental-implementation". Add task creation, task listing, and task editing to an application.
Expected outcome:
Using "incremental-implementation". Add a sharing feature that is not ready for all users.
Expected outcome:
Add the sharing path behind a disabled-by-default feature flag. Test the flag-off behavior, then verify the enabled path before wider release.
Using "incremental-implementation". A new WebSocket integration has uncertain reliability.
Expected outcome:
Start with a connection proof and its test. Add real-time updates only after the connection works, then add reconnection and offline behavior.
All 28 static findings are false positives caused by Markdown syntax, illustrative code, or ordinary implementation guidance. The skill contains no executable scripts, network behavior, secret handling, or prompt injection evidence.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/addyosmani-incremental-implementation/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-incremental-implementation?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-incremental-implementation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-incremental-implementation/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-incremental-implementation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>addyosmani. (2026). incremental-implementation security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-incremental-implementation/audits/2@techreport{addyosmani-addyosmani-incremental-implementation-2026,
author = {addyosmani},
title = {incremental-implementation security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/addyosmani-incremental-implementation/audits/2},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "incremental-implementation security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-incremental-implementation/audits/2"
identifiers:
- type: other
value: "skillstore:addyosmani-incremental-implementation:audit:2"
description: "Skillstore immutable audit report identifier"
Turn a large feature into complete vertical slices that can be tested and reviewed as they are built.
Use contract-first slicing to define shared interfaces before parallel implementation and integration.
Use risk-first slices, feature flags, and rollback-friendly changes when a task has uncertainty or incomplete functionality.
Help me split this change into the smallest complete increment. Identify the files, test, and verification step for the first increment.
Create a vertical-slice plan for this feature. Each slice must deliver working behavior, include tests, and remain reviewable.
Design a contract-first sequence for this frontend and backend change. Separate the contract, backend, frontend, and integration checks.
Analyze this implementation plan and reorder its increments by technical risk. Add feature flags, verification gates, and rollback points where needed.
Author
addyosmaniLicense
MIT
Skillstore revision
r2
Version notice
The author did not declare a version.
Ref
5d5054f8a23586f9b500fece1cb613a9dffc787b
Maintenance freshness
9/19/2026
Usage
1 downloads · 0 views
File structure
📄 SKILL.md
Review Code Across Five Quality Axes
Code reviews often miss risks when they focus only on tests or style. This skill guides a consistent review of correctness, readability, architecture, security, and performance.
Clarify User Intent Before You Build
Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.
Plan Work Into Verifiable Tasks
Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.
Document Decisions and Architecture Clearly
Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.
Build Accessible, Production-Ready Frontends
Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.
Debug Errors with a Root-Cause Workflow
Debugging failures by guesswork wastes time and can hide the real cause. This skill provides a repeatable process for reproducing, isolating, fixing, and verifying problems.
Build Reliable Test Automation
by 89jobrien
Weak tests slow releases and hide regressions. This skill guides test strategy, TDD, automation, coverage review, and Playwright web checks.
Plan Reliable Tests Across Your Codebase
by 0xDarkMatter
This skill helps teams choose test strategies, mocks, data fixtures, coverage gates, and CI patterns without mixing test scopes. It gives Claude, Codex, and Claude Code structured guidance for unit, integration, end-to-end, TDD, and pipeline testing.
Debug Technical Failures Systematically
by Asmayaseen
Quick fixes often hide the real cause and create regressions. This skill structures investigation, hypothesis testing, implementation, and verification around collected evidence.
Build Better Go Tests
by 89jobrien
Go teams need consistent tests across units, integrations, mocks, benchmarks, and coverage. This skill provides practical Go testing patterns that Claude, Codex, and Claude Code can apply during development.
Enforce Waterfall Phase Gates
by Chemiseblanc
AI coding sessions can skip requirements, design, or testing when pressure rises. This skill keeps work inside a strict waterfall flow with documented gates.
Build Python Tests with pytest TDD
by 89jobrien
Python teams often need consistent tests, coverage, and reports without losing TDD discipline. This skill provides pytest-focused workflows, examples, and reporting guidance for Claude, Codex, and Claude Code.