addyosmani/agent-skills✦ 精选0°

spec-driven-development

仓库创建 2026年2月16日最近提交 21 小时前SkillHot 收录 20 天前

⬈ GitHub 仓库 ⬈ SKILL.md 原文件 ⬇ Raw 原始文件

▸ 精选理由

作为共享的单一事实源，减少误解与返工，适合新功能启动。

这个 Skill 做什么

先编写结构化规格再编码，明确要做什么、为什么与完成标准。

先把要做的事情写成结构化的 spec，再开始编码，用文字明确目标、理由和验收标准。适合启动新项目、实现复杂功能或需求模糊时使用。好处是把模糊需求变成可验证的任务，团队有共同参照，开发方向和验收标准都清楚。

▸ 展开 SKILL.md 英文原文

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea.

开发编程规格先行需求明确验收准则通用

8.1w

Stars

8.7k

Forks

仓库内 Skill

+10.0k

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/addyosmani/agent-skills/main/skills/spec-driven-development/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/addyosmani/agent-skills/main/skills/spec-driven-development/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Spec-Driven Development

## Overview

Write a structured specification before writing any code. The spec is the shared source of truth between you and the human engineer — it defines what we're building, why, and how we'll know it's done. Code without a spec is guessing.

## When to Use

- Starting a new project or feature
- Requirements are ambiguous or incomplete
- The change touches multiple files or modules
- You're about to make an architectural decision
- The task would take more than 30 minutes to implement

**When NOT to use:** Single-line fixes, typo corrections, or changes where requirements are unambiguous and self-contained.

## The Gated Workflow

Spec-driven development has f

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有