What is spec-driven-develop?

A seven-phase workflow for planning and carrying out large project changes, such as rewrites, migrations, and major refactors.

Use it for large-scale project changes that need requirements, a plan, task tracking, instruction review, execution, and archived results.

It turns a broad transformation into documented analysis, tasks, progress tracking, implementation, and final checks before coding begins.

spec-driven-develop — Skill for Claude Code by zhu1090093659

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add zhu1090093659/spec_driven_develop --skill spec-driven-develop

Clone the repo

git clone --depth 1 https://github.com/zhu1090093659/spec_driven_develop

Made for: Claude Code.

Or install spec-driven-develop, the plugin that ships this one along with the rest of its 3 skills, 4 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/zhu1090093659/spec_driven_develop/spec-driven-develop/github.svg)](https://agentmods.dev/skills/zhu1090093659/spec_driven_develop/spec-driven-develop)

Your own site

<a href="https://agentmods.dev/skills/zhu1090093659/spec_driven_develop/spec-driven-develop"><img src="https://agentmods.dev/badge/skills/zhu1090093659/spec_driven_develop/spec-driven-develop/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/zhu1090093659/spec_driven_develop/spec-driven-develop"><img src="https://agentmods.dev/badge/skills/zhu1090093659/spec_driven_develop/spec-driven-develop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 148 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,551 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00148	$0.04551
Opus 5.5	$0.00059	$0.01820
Sonnet 5.5	$0.00030	$0.00910
Haiku 4.5	$0.00015	$0.00455

Measured 2mo ago against content hash 53861b7fd946, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

spec-driven-develop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/spec-driven-develop/skills/spec-driven-develop/SKILL.md · 250 lines

How it starts

The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec-Driven Develop

You are executing the Spec-Driven Development workflow — a seven-phase pipeline (Phases 0-6) for large-scale complex tasks. Complete preparation phases (analysis, planning, progress setup), then execute the plan — all within a single session.

Behavioral rules: references/behavioral-rules.md — read and follow them in every phase; they are non-negotiable.

Configuration

Path	Default Value	Purpose
Analysis output	`docs/analysis/`	Phase 1 analysis documents
Plan output	`docs/plan/`	Phase 3 planning documents
Progress output	`docs/progress/`	Phase 4 tracking documents (incl. MASTER.md)
Instruction surfaces	Resolved per project	Project-level constraints for agents (see Phase 4)
Memory surface	Native first	Durable facts via the agent's native memory when available; repo fallback only when explicitly selected
Archive output	`docs/archives/<project>/`	Phase 6 archived artifacts
Task tracking mode	Auto-detect	`GITHUB_FULL`, `GITHUB_STANDARD`, or `LOCAL_ONLY`
Delivery batching	Phase-first	Issues track tasks; PRs integrate coherent task batches
Adaptive control	Enabled	Drift thresholds: annotate=20%, replan=40%, rescope=60% of phase tasks

Canonical references (each topic has exactly one home — cite it, never re-explain it):

Reference	Owns
`references/behavioral-rules.md`	All behavioral rules (1-19)
`references/github-integration.md`	Tracking modes, pre-flight check, all `gh` commands and Issue/PR body templates
`references/adaptive-control.md`	Telemetry collection, drift calculation, response actions, state storage, controller activation
`references/parallel-protocol.md`	Dispatch/review admission (tiers), lane/worktree protocol, review loop, merge risk, post-integration checks
`references/super-philosophy.md`	S.U.P.E.R principles + the 10-check review checklist
`references/templates/`	Schemas for every generated document (analysis, plan, progress, governance, archive)

Read the full file on GitHub · 250 lines

Files

What ships with it

10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 250 lines · 148 tokens per session scan A 53861b7fd946

Subscribe to this mod's changes

spec-driven-develop is a skill published in the GitHub repository zhu1090093659/spec_driven_develop (993 stars, last pushed 3mo ago), licensed MIT. It adds 148 tokens to every session and 4,551 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Planning ai-agent ai-coding-assistant codex skills spec-driven-development

spec-driven-develop next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spec-driven-developzhu1090093659/spec_driven_develop	Skill	993	3mo ago	MIT	A	148	Claude Code
build-executorMageByte-Zero/spec-superflow	Skill	879	5d ago	MIT	A	30	Claude Code
contract-builderMageByte-Zero/spec-superflow	Skill	879	5d ago	MIT	A	33	Claude Code
codex-issue-coordinatorowainlewis/blueprint	Skill	426	4d ago	MIT	A	59	Claude Code, Codex
html-docowainlewis/blueprint	Skill	426	4d ago	MIT	A	51	Claude Code, Codex
reviewowainlewis/blueprint	Skill	426	4d ago	MIT	A	58	Claude Code, Codex
architectureowainlewis/blueprint	Skill	426	4d ago	MIT	A	52	Claude Code, Codex