원클릭으로
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 페이지를 검토하고 설치를 진행할 수 있습니다.
Scaffold 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.
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 spec