Plan Software Work With Clear Specifications
Unclear requirements cause rework, missed assumptions, and poorly ordered implementation tasks. This skill guides teams through reviewed specifications, dependency-aware plans, and verifiable tasks before coding.
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "spec-driven-development" from https://skillstore.io/skills/addyosmani-spec-driven-development.md and its manifest at https://skillstore.io/api/skills/addyosmani-spec-driven-development/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.
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Usando "spec-driven-development". Make the dashboard faster.
Resultado esperado:
Success criteria: largest contentful paint under 2.5 seconds on a 4G connection; initial data load under 500 milliseconds; cumulative layout shift under 0.1.
Usando "spec-driven-development". Build account, billing, notifications, and reporting capabilities.
Resultado esperado:
All 26 static findings are false positives. The flagged backticks are Markdown code formatting and inline references in a documentation workflow, not shell execution or system reconnaissance.
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.
https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-spec-driven-development?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/addyosmani-spec-driven-development?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-spec-driven-development/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/addyosmani-spec-driven-development.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). spec-driven-development security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2@techreport{addyosmani-addyosmani-spec-driven-development-2026,
author = {addyosmani},
title = {spec-driven-development security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/addyosmani-spec-driven-development/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: "spec-driven-development security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-19"
url: "https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2"
identifiers:
- type: other
value: "skillstore:addyosmani-spec-driven-development:audit:2"
description: "Skillstore immutable audit report identifier"
Cada autor sigue siendo un skill instalable independiente. La variante recomendada se ordena según la evidencia de Skillstore.
Por qué esta variante es la primera
89jobrien-spec-driven-development
2026-10-19
addyosmani-spec-driven-development
2026-09-22
Turn an initial feature idea into an approved specification with user goals, boundaries, success criteria, and an implementation plan.
Map independently testable capabilities, record dependency direction, and create module-specific specifications in build order.
Convert vague outcomes into measurable acceptance criteria, verification steps, and focused implementation tasks.
Create a concise specification for this feature: [feature]. Ask clarifying questions first, then define the objective, users, scope, success criteria, and open questions.
Review this request: [request]. List the assumptions you would need to confirm, ask focused questions, and reframe the final requirements as testable success criteria.
Decompose this initiative into independently testable modules: [initiative]. Create a capability map with stable identifiers, dependencies, build order, and a specification outline for each module.
Using this approved specification and plan: [documents], create dependency-ordered tasks. Give each task acceptance criteria, a verification step, and the files or areas likely to change.
Autor
addyosmaniLicencia
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
0 descargas · 0 vistas
Estructura de archivos
📄 SKILL.md
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.
Revisar código según cinco ejes de calidad
Los cambios de código pueden ocultar problemas de corrección, seguridad, arquitectura, legibilidad y rendimiento. Esta habilidad aplica un proceso de revisión estructurado y genera comentarios priorizados y prácticos.
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.
Harden Applications Against Security Risks
Security reviews can miss trust boundaries and unsafe data flows. This skill supplies threat-modeling prompts, OWASP patterns, and practical review checklists.
Planificación de requisitos con preguntas interactivas
por DNYoussef
Las solicitudes de proyectos ambiguas suelen provocar requisitos faltantes y retrabajo. Esta skill guía a Claude, Codex y Claude Code mediante lotes de preguntas estructuradas.
Convertir ideas en diseños validados
por ZhanlinCui
Las ideas iniciales de producto e ingeniería a menudo fallan porque los requisitos siguen siendo vagos. Esta habilidad guía a Claude, Codex o Claude Code mediante preguntas enfocadas, opciones y un diseño validado antes de la implementación.
Pon a Prueba los Planes con Preguntas Enfocadas
por mattpocock
Los planes poco claros suelen ocultar suposiciones arriesgadas y dependencias sin resolver. Esta skill guía a Claude, Codex o Claude Code con una pregunta enfocada a la vez.
Organiza GitHub Issues con etiquetas
por C0ntr0lledCha0s
Los repositorios grandes pierden tiempo cuando las incidencias usan etiquetas inconsistentes e hitos poco claros. Esta skill ayuda a crear taxonomías, ejecutar actualizaciones masivas e informar el progreso mediante flujos de trabajo de GitHub.
Seguimiento de requisitos de funciones en YAML
por Chemiseblanc
Los equipos pierden la intención del proyecto cuando los requisitos viven solo en chats o listas de tareas. Esta skill mantiene el alcance, las pruebas, las decisiones y el progreso en un archivo features.yml persistente.
Planificar versiones de producto
por yunshu0909
Las ideas de producto suelen volverse demasiado amplias antes de que una primera versión esté clara. Esta skill convierte requisitos en planes escalonados de MVP, iteración y V1.0 con puntos de validación.