技能 spec-driven-development

📦

spec-driven-development

Name: spec-driven-development
Author: addyosmani

內容修訂 r2 安全 ⚙️ 外部命令

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.

支援: Claude Codex Code(CC)

🥉 78 銅級

Maintain this Skill? Claim it 🥉 78 銅級

使用我的智慧代理安裝

將此請求複製給你的智慧代理，其中包含權威 Skill 頁面和清單。

智能體請求

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.

你的智慧代理仍應顯示其計畫，並依安全政策請求必要確認。

Agent 可讀資源

當 AI Agent、爬蟲或腳本需要乾淨脈絡、而不是讀取完整頁面時，請使用這些連結。

Markdown 詳情 GET /skills/addyosmani-spec-driven-development.md 已簽名 manifest GET /api/skills/addyosmani-spec-driven-development/manifest 已簽名 lockfile GET /api/skills/addyosmani-spec-driven-development/lockfile

測試它

正在使用「spec-driven-development」。 Make the dashboard faster.

預期結果:

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」。 Build account, billing, notifications, and reporting capabilities.

預期結果:

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.

安全審計

安全

v2 • 2026/9/19 開啟版本化報告

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.

已掃描檔案

252

分析行數

複核項目

已忽略的誤報

最近一次完成的靜態與語意稽核未偵測到已確認的安全發現。這並不能證明該 Skill 沒有副作用。

審計單位: codex 檢視審計紀錄 →

分享與引用此報告

分享版本化評估報告、中性徽章、嵌入卡片與引用。Skillstore 只報告證據，不判斷該 Skill 是否安全。

開啟版本化報告

複製報告連結

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

Markdown 徽章

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

HTML 徽章

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

學術引用 (APA · BibTeX · CFF)

APA 引用

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

BibTeX 引用

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

比較變體

2 個可安裝變體

每位作者的技能都保留為獨立的可安裝項目。推薦變體依 Skillstore 證據排序。

為何此變體排名第一

Skillstore 評分最高

作者 / 來源 Skillstore 評分證據置信度 Skillstore 使用量已更新

Joseph OBrien 推薦

89jobrien-spec-driven-development

Skillstore 評分 81

證據置信度高

Skillstore 使用量 30

已更新

2026-10-19

addyosmani 目前

addyosmani-spec-driven-development

Skillstore 評分 78

證據置信度中

Skillstore 使用量 6

已更新

2026-09-22

Skillstore 評分

評分依據證據置信度: 中

架構

可維護性

內容

社群

規範符合度

你可以打造什麼

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.

試試這些提示

Draft a Basic Specification

Create a concise specification for this feature: [feature]. Ask clarifying questions first, then define the objective, users, scope, success criteria, and open questions.

Clarify an Ambiguous Request

Review this request: [request]. List the assumptions you would need to confirm, ask focused questions, and reframe the final requirements as testable success criteria.

Plan a Multi-Module Change

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.

Prepare Implementation Tasks

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.

最佳實務

Confirm assumptions before drafting specification content.
Use stable module identifiers and explicit dependency direction.
Require human approval at each phase before advancing.

避免

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.

常見問題

When should I use this skill?

Use it for new projects, significant features, ambiguous requirements, or changes that span multiple modules.

When should I skip it?

Skip it for single-line fixes, typo corrections, and small changes with clear requirements.

Does it write production code?

No. It prepares specifications, plans, tasks, and review gates before implementation.

What does the specification include?

It covers the objective, commands, project structure, code style, testing strategy, boundaries, success criteria, and open questions.

How does it handle large initiatives?

It creates a capability map, records dependencies, sets a build order, and creates a specification for each module.

Does it replace technical review?

No. Human reviewers still approve assumptions, scope, architecture, security concerns, and readiness for implementation.

開發者詳細資訊

作者

addyosmani

授權

MIT

Skillstore 修訂

版本提示

作者未聲明版本。

儲存庫

https://github.com/addyosmani/agent-skills/tree/c004a74784a08295d52749b04cda634125b9a581/skills/spec-driven-development

引用

5d5054f8a23586f9b500fece1cb613a9dffc787b

維護新鮮度

2026/9/19

使用量

0 次下載 · 0 次瀏覽

檔案結構

📄 SKILL.md

addyosmani 的更多技能

查看全部

📦

interview-me

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.

溝通查看

📦

code-review-and-quality

依五大品質面向審查程式碼

程式碼變更可能隱藏正確性、安全性、架構、可讀性與效能問題。此 skill 採用結構化的審查流程，並產出依優先順序排列且可採取行動的意見。

程式開發查看

📦

planning-and-task-breakdown

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.

效率查看

📦

documentation-and-adrs

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.

文件查看

📦

frontend-ui-engineering

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.

設計與創意查看

📦

using-agent-skills

Discover and Apply Agent Skills

Teams often lose time choosing the right workflow for a software task. This skill maps task context to focused agent skills and a practical development sequence.

程式開發查看

查看全部

📦