spec-driven-development SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

spec-driven-development from naimkatiman/continuous-improvement is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add naimkatiman/continuous-improvement/spec-driven-development@git:20260507.4a6727c

Pins git:20260507.4a6727c in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

naimkatiman/continuous-improvement

Path

third-party/addy-agent-skills/skills/spec-driven-development/SKILL.md

Versions recorded

1

Latest version

git:20260507.4a6727c, committed May 7, 2026

Size

7,660 bytes

Repository stars

9

License

MIT

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.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# 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 four phases. Do not advance to the next phase until the current one is validated.

```
SPECIFY ──→ PLAN ──→ TASKS ──→ IMPLEMENT
   │          │        │          │
   ▼          ▼        ▼          ▼
 Human      Human    Human      Human
 reviews    reviews  reviews    reviews
```

### Phase 1: Specify

Start with a high-level vision. Ask the human clarifying questions until requirements are concrete.
…

Read the whole file at its exact version.

How to install

mdr add naimkatiman/continuous-improvement/spec-driven-development@sha256:6d098845420d0f7b

[![mdr](https://markdownregistry.com/badge/art_xxjddcbksylzhm4t.svg)](https://markdownregistry.com/a/art_xxjddcbksylzhm4t)

Versions

The registry has recorded 1 version of this file, committed on May 7, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_xxjddcbksylzhm4t
GET https://markdownregistry.com/api/v1/resolve?ref=naimkatiman/continuous-improvement/spec-driven-development
GET https://markdownregistry.com/api/v1/blob/6d098845420d0f7bbdedfcb8a80bee391b4e9aff58a8195638b35a7bfd7b9b59

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from naimkatiman/continuous-improvement

Every file in naimkatiman/continuous-improvement

Other files named spec-driven-development

Browse by kind, by grade A, or by owner.