spec-driven-development

仓库创建 2026年7月5日最近提交 21 天前SkillHot 收录 21 天前

▸ 精选理由

适合新项目或模糊需求场景，减少返工与误解。

这个 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.

Skill 开发管理规格需求验收通用

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

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

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/kulapoo/opencode-agent-harness/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 公开信息 · 原文版权归作者所有