一键导入
spec-driven-dev
Drive any non-trivial change through write-spec → review-spec → implement-from-spec, instead of jumping to code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Drive any non-trivial change through write-spec → review-spec → implement-from-spec, instead of jumping to code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | spec-driven-dev |
| description | Drive any non-trivial change through write-spec → review-spec → implement-from-spec, instead of jumping to code. |
| license | MIT |
| user-invocable | true |
Use when the user asks for any change touching more than one file, or any feature whose behavior is not obvious from a one-line description.
Jumping to code skips the cheapest place to catch a misunderstanding: before any code exists. A short spec is faster than a wrong implementation.
Produce a markdown spec with these sections:
(new).Save the spec to docs/specs/<short-name>.md. Stop. Show it to the user.
Wait for the user to:
Do not proceed to implementation while open questions exist. Update the spec in place.
## Deviations section.docs/specs/<name>.mdFiles touched were modifiedFiles touched mid-implementation without updating the specScaffold a REST API endpoint with input validation, structured error handling, and a passing test before any business logic is written.
Review a Dockerfile against an enterprise best-practice checklist and report concrete issues with line references.