Home / hamza-ali-shahjahan / hamzaish · GitHub

spec-driven-development SKILL.md skillA

spec-driven-development from hamza-ali-shahjahan/hamzaish is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add hamza-ali-shahjahan/hamzaish/spec-driven-development@git:20260721.96f6808

Pins git:20260721.96f6808 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: hamza-ali-shahjahan/hamzaish
Path: factory/skills/spec-driven-development/SKILL.md
Versions recorded: 3
Latest version: git:20260721.96f6808, committed Jul 21, 2026
First version recorded: Jun 27, 2026
Size: 8,603 bytes
Repository stars: 10
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

The exact contents, by fingerprint

mdr add hamza-ali-shahjahan/hamzaish/spec-driven-development@sha256:505939e15bf6b8ae

The line at the top of this page pins the label git:20260721.96f6808, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

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

4 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Jun 27, 2026 and Jul 21, 2026, about one every 12 days.

version	committed	commit	size	audit
git:20260721.96f6808 latest	2026-07-21	96f6808	8,603 B	A	view · diff
git:20260714.8c6da21	2026-07-14	8c6da21	8,040 B	A	view · diff
git:20260627.bd6e9ea	2026-06-27	bd6e9ea	7,660 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (8603 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

hamza-ali-shahjahan/hamzaish · 10 stars · license MIT · pushed 2026-10-07 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jgaogfnb7dvygdad
GET https://markdownregistry.com/api/v1/resolve?ref=hamza-ali-shahjahan/hamzaish/spec-driven-development
GET https://markdownregistry.com/api/v1/blob/505939e15bf6b8ae75344722e97e4a4efa721aff9a31b7e61a01c5b41b284b40

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 hamza-ali-shahjahan/hamzaish

hamzaish Cursor rule

hamza-ali-shahjahan/hamzaish · .cursor/rules/hamzaish.mdc · Hamzaish factory — universal operating context for any agent working in this repo

git:20260614.1c0c7ab · audit A · 10 stars

AGENTS.md AGENTS.md file

hamza-ali-shahjahan/hamzaish · AGENTS.md

git:20260921.82b1475 · audit A · 10 stars

CLAUDE.md CLAUDE.md file

hamza-ali-shahjahan/hamzaish · CLAUDE.md

git:20261007.6b62766 · audit A · 10 stars

CLAUDE.md@_archive/v0 CLAUDE.md file

hamza-ali-shahjahan/hamzaish · _archive/v0/CLAUDE.md