Compétences incremental-implementation
📩

incremental-implementation

RĂ©vision du contenu r2 SĂ»r ⚡ Contient des scripts⚙ Commandes externes📁 AccĂšs au systĂšme de fichiers🔑 Variables d’environnement

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.

Prend en charge: Claude Codex Code(CC)
Maintain this Skill? Claim it đŸ„‰ 78 Bronze

Installer avec mon Agent

Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.

Demande d’agent
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.

Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.

Ressources lisibles par les agents

Utilisez ces liens lorsqu’un Agent IA, un crawler ou un script a besoin d’un contexte propre au lieu de lire toute la page.

Tester

Utilisation de « incremental-implementation ». Add task creation, task listing, and task editing to an application.

Résultat attendu:

  • 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.

Utilisation de « incremental-implementation ». Add a sharing feature that is not ready for all users.

Résultat attendu:

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

Utilisation de « incremental-implementation ». A new WebSocket integration has uncertain reliability.

Résultat attendu:

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

Audit de sécurité

Sûr
v2 ‱ 19/09/2026 Ouvrir le rapport versionnĂ©

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
Fichiers analysés
250
Lignes analysées
0
ÉlĂ©ments Ă  examiner
0
Faux positifs ignorés
Le dernier audit statique et sĂ©mantique terminĂ© n’a dĂ©tectĂ© aucun constat de sĂ©curitĂ© confirmĂ©. Cela ne prouve pas que le skill est sans effets secondaires.
Partager et citer ce rapport

Partagez le rapport d’évaluation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.

Ouvrir le rapport versionné
Évaluation de sĂ©curitĂ©

Copier le lien du rapport

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

Badge Markdown

[![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)

Badge HTML

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

Carte intégrable

<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>
Citations académiques (APA · BibTeX · CFF)

Citation APA

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

Citation BibTeX

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

Score Skillstore

Pourquoi ce score Niveau de confiance des preuves: Moyen
55
Architecture
85
Maintenabilité
87
Contenu
65
Communauté
91
Conformité aux spécifications

Ce que vous pouvez créer

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.

Essayez ces prompts

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.

Bonnes pratiques

  • 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.

Éviter

  • 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.

Foire aux questions

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.

Détails du développeur

Auteur

addyosmani

Licence

MIT

Révision Skillstore

r2

Avis de version

L’auteur n’a dĂ©clarĂ© aucune version.

Réf

5d5054f8a23586f9b500fece1cb613a9dffc787b

Récence de maintenance

19/09/2026

Utilisation

1 téléchargements · 0 vues

Structure de fichiers

📄 SKILL.md