spec-driven-development
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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.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
„spec-driven-development“ wird verwendet. Make the dashboard faster.
Erwartetes Ergebnis:
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.
„spec-driven-development“ wird verwendet. Build account, billing, notifications, and reporting capabilities.
Erwartetes Ergebnis:
- Capability map: identity owns accounts and sessions; billing depends on identity; notifications depends on identity; reporting depends on billing and notifications.
- Build order: identity, then billing and notifications, then reporting.
Sicherheitsaudit
SicherAll 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.
Risikofaktoren
⚙️ Externe Befehle (23)
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.
Berichtslink kopieren
https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/addyosmani-spec-driven-development?utm_source=security_passport_badge)HTML-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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
addyosmani. (2026). spec-driven-development security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-spec-driven-development/audits/2BibTeX-Zitat
@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}
}CITATION.cff
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"
Varianten vergleichen
2 installierbare VariantenJeder Autor bleibt ein eigener installierbarer Skill. Die empfohlene Variante wird nach Skillstore-Nachweisen bewertet.
Warum diese Variante zuerst steht
89jobrien-spec-driven-development
2026-10-19
addyosmani-spec-driven-development
2026-09-22
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
Shape a New Product Feature
Turn an initial feature idea into an approved specification with user goals, boundaries, success criteria, and an implementation plan.
Decompose a Multi-Module Initiative
Map independently testable capabilities, record dependency direction, and create module-specific specifications in build order.
Make Requirements Testable
Convert vague outcomes into measurable acceptance criteria, verification steps, and focused implementation tasks.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- Confirm assumptions before drafting specification content.
- Use stable module identifiers and explicit dependency direction.
- Require human approval at each phase before advancing.
Vermeiden
- Starting implementation before requirements and success criteria are approved.
- Hiding ambiguous decisions inside a specification without asking.
- Creating tasks without acceptance criteria or a verification step.
Häufig gestellte Fragen
When should I use this skill?
When should I skip it?
Does it write production code?
What does the specification include?
How does it handle large initiatives?
Does it replace technical review?
Entwicklerdetails
Autor
addyosmaniLizenz
MIT
Skillstore-Revision
r2
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
5d5054f8a23586f9b500fece1cb613a9dffc787b
Aktualität der Wartung
19.9.2026
Nutzung
0 Downloads · 0 Aufrufe
Dateistruktur
đź“„ SKILL.md