技能 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 青铜

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 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 使用量 22

已更新

2026-09-09

addyosmani 当前

addyosmani-spec-driven-development

Skillstore 评分 78

证据置信度中

Skillstore 使用量 2

已更新

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 的更多技能

查看全部

📦

code-review-and-quality

从五个质量维度审查代码

代码变更可能隐藏正确性、安全性、架构、可读性和性能问题。此技能采用结构化审查流程，并提供按优先级排列、可执行的反馈。

编码与开发查看

📦

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.

沟通查看

📦

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.

设计与创意查看

📦

security-and-hardening

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.

安全与合规查看

查看全部

📦