Habilidades incremental-implementation
📦

incremental-implementation

Revisión del contenido r2 Seguro ⚡ Contiene scripts⚙️ Comandos externos📁 Acceso al sistema de archivos🔑 Variables de entorno

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.

Compatible con: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 Bronce

Instalar con mi Agente

Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.

Solicitud de agente
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.

Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.

Recursos legibles por agentes

Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.

Pruébalo

Usando "incremental-implementation". Add task creation, task listing, and task editing to an application.

Resultado esperado:

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

Usando "incremental-implementation". Add a sharing feature that is not ready for all users.

Resultado esperado:

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

Usando "incremental-implementation". A new WebSocket integration has uncertain reliability.

Resultado esperado:

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

Auditoría de seguridad

Seguro

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
Archivos escaneados
250
Líneas analizadas
0
Elementos de revisión
0
Falsos positivos ignorados
La auditoría estática y semántica completada más reciente no detectó hallazgos de seguridad confirmados. Esto no demuestra que el skill no tenga efectos secundarios.
Compartir y citar este informe

Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.

Abrir el informe versionado
Evaluación de seguridad

Copiar enlace del informe

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

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

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

Tarjeta para insertar

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

Cita APA

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

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

Puntuación de Skillstore

Por qué esta puntuación Confianza de la evidencia: Medio
55
Arquitectura
85
Mantenibilidad
87
Contenido
65
Comunidad
91
Cumplimiento de la especificación

Lo que puedes crear

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.

Prueba estos 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.

Mejores prácticas

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

Evitar

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

Preguntas frecuentes

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.

Detalles del desarrollador

Licencia

MIT

Revisión de Skillstore

r2

Aviso de versión

El autor no declaró una versión.

Ref.

5d5054f8a23586f9b500fece1cb613a9dffc787b

Actualidad del mantenimiento

19/9/2026

Uso

1 descargas · 0 vistas

Estructura de archivos

📄 SKILL.md