Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add vinvcn/addyosmani-agent-skills-zh --skill spec-driven-developmentgit clone --depth 1 https://github.com/vinvcn/addyosmani-agent-skills-zhWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vinvcn/addyosmani-agent-skills-zh/spec-driven-development)<a href="https://agentmods.dev/skills/vinvcn/addyosmani-agent-skills-zh/spec-driven-development"><img src="https://agentmods.dev/badge/skills/vinvcn/addyosmani-agent-skills-zh/spec-driven-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/vinvcn/addyosmani-agent-skills-zh/spec-driven-development"><img src="https://agentmods.dev/badge/skills/vinvcn/addyosmani-agent-skills-zh/spec-driven-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00092 | $0.03147 |
| Opus 5.5 | $0.00037 | $0.01259 |
| Sonnet 5.5 | $0.00018 | $0.00629 |
| Haiku 4.5 | $0.00009 | $0.00315 |
Grade A, and why
spec-driven-development scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
3 near-identical copies found in the catalogue:
- spec-driven-development — 98% identical, 247 lines differ
- spec-writing — 97% identical, 289 lines differ
- spec-writing — 97% identical, 289 lines differ
How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Development
概览
在编写任何代码之前，先写一份结构化规格说明。spec 是你和人类工程师之间共享的事实来源，它定义我们要构建什么、为什么构建，以及如何知道它完成了。没有 spec 的代码就是猜测。
何时使用
- 开始一个新项目或功能
- 需求有歧义或不完整
- 变更触及多个文件或模块
- 你即将做出架构决策
- 任务实现需要超过 30 分钟
何时不要使用： 单行修复、拼写更正，或需求明确且自包含的变更。
门控工作流
Spec-driven development 有四个阶段，前面还有一个范围检查（阶段 0），它只在一个请求打包了多个可独立测试的能力时才会激活。当前阶段被验证之前，不要进入下一阶段。
SPECIFY ──→ PLAN ──→ TASKS ──→ IMPLEMENT
│ │ │ │
▼ ▼ ▼ ▼
Human Human Human Human
reviews reviews reviews reviews
阶段 0：范围检查（Scope Check）
大多数请求只描述一个能力。如果当前的请求也是如此，跳过这个阶段，直接进入 Specify。阶段 0 是为例外情况存在的，不是常规；它不会给单能力功能强加层级结构。
检测。 当一个需求打包了多个可独立测试的能力时，先分解再做规格说明：
- 需求点名了多个各有自己的消费者或数据的独立能力（例如 identity、billing、notifications、reporting）
- 验收标准聚成可以分别交付和验证的组
- 砍掉或替换某一个能力，不需要重写其他能力的要求
在写任何 spec 之前，先提出一份能力地图（capability map）。 要小、可评审：一张模块表加一个构建顺序，不是项目计划：
# Capability Map: [Initiative Name]
| Module id | Responsibility | Depends on |
|---|---|---|
| identity | Accounts, sessions, SSO | — |
| billing | Plans, invoices, payments | identity |
| notifications | Email and webhook fan-out | identity |
| reporting | Usage dashboards | billing, notifications |
Build order: identity → billing, notifications → reporting
- 稳定的模块 id。 kebab-case，一次选定，initiative 进行中绝不重命名。Specs、计划和下游命令都通过这些 id 来选择工作，而不是猜测当前哪个 spec 生效。
- 依赖有方向，无环。 箭头只指向一个方向。如果两个模块互相依赖，它们其实是一个模块。
- 接口位于边界上。 地图记录
billing依赖identity；两者之间的契约属于提供方模块的 spec（设计方法见api-and-interface-design）。
地图和其他阶段一样有门禁。 在写任何模块 spec 之前，由人类评审模块边界、依赖方向和构建顺序。地图搞错的代价很高；评审十行则不然。
然后按模块递归。 依依赖顺序为每个模块执行 Specify → Plan → Tasks → Implement。每个模块都有自己的 spec，范围限定在该模块的目标、边界和成功标准。把批准后的地图保存在项目根目录，各模块的 spec 与之放在一起，按模块 id 命名（SPEC-identity.md、SPEC-billing.md）。存在的索引是这张地图，而不是靠猜文件名。
阶段 1：Specify
从高层愿景开始。向人类提出澄清问题，直到需求具体。
立即暴露假设。 在写任何 spec 内容之前，列出你的假设：
ASSUMPTIONS I'M MAKING:
1. This is a web application (not native mobile)
2. Authentication uses session-based cookies (not JWT)
3. The database is PostgreSQL (based on existing Prisma schema)
4. We're targeting modern browsers only (no IE11)
→ Correct me now or I'll proceed with these.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago Changed · +8 lines 7fe3f3e93652
- 1mo ago Changed · +47 lines · +44 tokens per session bc9bb6713fdb
- 1mo ago First seen · 201 lines · 48 tokens per session scan A 000f3793e18d
spec-driven-development is a skill published in the GitHub repository vinvcn/addyosmani-agent-skills-zh (44 stars, last pushed 7d ago), licensed MIT. It adds 92 tokens to every session and 3,147 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
test-driven-development
Drives development with tests via Red-Green-Refactor and the Prove-It pattern, with hard rules against weakening assertions or faking green suites. Use when implementing any logic, fixing any bug, or changing any behavior. Triggers on "add a feature", "fix this bug", "write tests", or any task where done must be…
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
data-engineering
Guides data pipeline design, ETL/ELT workflows, schema evolution, and data quality assurance. Use when building data pipelines, designing data warehouses, migrating schemas, or ensuring data integrity across systems. Use when you need reliable, testable, and observable data flows.
debugging-and-error-recovery
Guides systematic root-cause debugging with hard rules against guess-fixes and symptom suppression. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Triggers on "this is broken", "tests are failing", "why doesn't this work", or any error output.
ai-ops
Guides operational excellence for AI/ML systems in production. Use when deploying models, managing inference infrastructure, monitoring model drift, or maintaining AI-powered features. Use when you need reliable, observable, and governable machine learning systems.