Fähigkeiten incremental-implementation
📦

incremental-implementation

Inhaltsrevision r2 Sicher ⚡ Enthält Skripte⚙️ Externe Befehle📁 Dateisystemzugriff🔑 Umgebungsvariablen

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.

Unterstützt: Claude Codex Code(CC)
🥉 78 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
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.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Testen

„incremental-implementation“ wird verwendet. Add task creation, task listing, and task editing to an application.

Erwartetes Ergebnis:

  • Increment 1: create a task through the database, API, and basic interface.
  • Increment 2: list tasks through the query, API, and interface.
  • Increment 3: edit a task with focused tests and verification.

„incremental-implementation“ wird verwendet. Add a sharing feature that is not ready for all users.

Erwartetes Ergebnis:

Add the sharing path behind a disabled-by-default feature flag. Test the flag-off behavior, then verify the enabled path before wider release.

„incremental-implementation“ wird verwendet. A new WebSocket integration has uncertain reliability.

Erwartetes Ergebnis:

Start with a connection proof and its test. Add real-time updates only after the connection works, then add reconnection and offline behavior.

Sicherheitsaudit

Sicher
v2 • 19.9.2026 Versionsbericht öffnen

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.

1
Gescannte Dateien
250
Analysierte Zeilen
0
Prüfelemente
0
Falschmeldungen ignoriert
Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.
Geprüft von: codex Audit-Verlauf anzeigen →
Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

https://skillstore.io/skills/addyosmani-incremental-implementation/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-incremental-implementation/security.svg)](https://skillstore.io/skills/addyosmani-incremental-implementation?utm_source=security_passport_badge)

HTML-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>

Einbettungskarte

<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>
Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

addyosmani. (2026). incremental-implementation security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-incremental-implementation/audits/2

BibTeX-Zitat

@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} }

CITATION.cff

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"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
91
Spezifikationskonformität

Was Sie erstellen können

Plan a Multi-File Feature

Turn a large feature into complete vertical slices that can be tested and reviewed as they are built.

Coordinate Frontend and Backend Work

Use contract-first slicing to define shared interfaces before parallel implementation and integration.

Reduce Delivery Risk

Use risk-first slices, feature flags, and rollback-friendly changes when a task has uncertainty or incomplete functionality.

Diese Prompts ausprobieren

Start a Small Change
Help me split this change into the smallest complete increment. Identify the files, test, and verification step for the first increment.
Plan Vertical Slices
Create a vertical-slice plan for this feature. Each slice must deliver working behavior, include tests, and remain reviewable.
Use a Contract First
Design a contract-first sequence for this frontend and backend change. Separate the contract, backend, frontend, and integration checks.
Prioritize Technical Risk
Analyze this implementation plan and reorder its increments by technical risk. Add feature flags, verification gates, and rollback points where needed.

Bewährte Praktiken

  • Keep every increment complete, testable, and independently reviewable.
  • Address the riskiest or most uncertain technical assumption early.
  • Use explicit scope, verification gates, feature flags, and rollback points.

Vermeiden

  • Implementing an entire multi-file feature before testing.
  • Combining unrelated refactors, configuration changes, and features.
  • Adding abstractions or scope before a real use case requires them.

Häufig gestellte Fragen

When should I use this skill?
Use it for multi-file features, refactors, feature flags, or tasks that feel too large to complete safely in one pass.
What is a vertical slice?
A vertical slice is a small change that travels through the required layers and leaves working user-visible behavior.
Should every increment be committed?
The skill recommends descriptive commits after verified increments so each change remains understandable and reversible.
How does contract-first slicing help?
It gives parallel teams a shared interface before they implement separate backend and frontend pieces.
When should I use a feature flag?
Use a flag when incomplete functionality must be merged without exposing it to users.
Does this skill run project commands?
No. It recommends that the agent discover and run the repository's own tests, build, type-check, and lint commands.

Entwicklerdetails

Lizenz

MIT

Skillstore-Revision

r2

Versionshinweis

Der Autor hat keine Version angegeben.

Ref.

5d5054f8a23586f9b500fece1cb613a9dffc787b

Aktualität der Wartung

19.9.2026

Nutzung

1 Downloads · 0 Aufrufe

Dateistruktur

📄 SKILL.md

Mehr von addyosmani

Alle anzeigen
Alle anzeigen