Individual skill

spec-driven

Use when starting a project or feature, requirements are unclear, or a change crosses modules. Not for implementing from an existing spec: use spec-driven-implementation.

.devin/skills/spec-driven/SKILL.md

Read pinned source

Source commit b0e8ce89a19fac880251dc3ea1babfeb4503a4fe

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Sep 28, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Spec-driven development

## Contract

| Field | Bound contract |
|---|---|
| Trigger | A new project or feature is starting, requirements are unclear, the change touches multiple modules, or the task exceeds roughly 30 minutes. |
| Authority | Reversible local: writes only files and VCS scoped to the current working tree; rollback is version control. No remote mutation, credential exposure, or irreversible action. |
| Side effect | Writes and commits a spec, records human-approved plan and tasks, and implements through offensive-first TDD. All writes are local; no external service calls. |
| Done | A reviewed, approved spec covering six areas is saved to the repo and the implementation follows it. |

## Inputs

The user's request is mandatory. The requester must approve the spec before planning begins.
Back to top