A Claude-native implementation of Spec-Driven Generation (SDG) — a structured process for building software by maintaining a master specification and letting AI generate everything else: the spec, the test spec, the certifications, the test harness, and the product. Humans answer clarifying questions to remove ambiguity; they do not write code or specs by hand.
This repository is the template. Dropped into a project, it makes every Claude Code session in that project run the SDG process automatically — no commands to learn, no CLI. You chat; the process does the rest.
specs/PROCESS.md— the harness-agnostic process specification (authoritative, immutable).specs/CLAUDE-PROCESS.md— how the process binds to Claude Code: the main thread is a "dumb" Orchestrator that only steps through phases; a forked Liaison subagent owns all Developer communication andspecs/PHILOSOPHY.md; Reviewer, Driver, Engineer, and Specialist run as fresh-context subagents driven by per-phase mission prompts in.claude/prompts/.CLAUDE.md— marks the project as SDG-governed, end to end, all or nothing.
Defaults: every agent runs Claude Fable (max effort for the session/Liaison/Reviewer, high elsewhere), and .claude/settings.json sets bypassPermissions — this is built to run unattended in a sandboxed or cloud environment (Claude Code web, a container, a VM). Adjust settings.json if that doesn't describe your machine.
Use the sdg-bootstrap skill (in sdg-bootstrap/) — share it with Claude and ask it to set up SDG in your project. Or do it manually:
# in your new project directory
npx degit modularcloud/sdg-claude sdg-tmp
rsync -a --exclude README.md --exclude LICENSE --exclude sdg-bootstrap sdg-tmp/ ./ && rm -rf sdg-tmpThen make sure the project is a git repository with a GitHub remote and Actions enabled, open Claude Code in it, and describe what you want to build.
Requirements: Claude Code (web or CLI) with access to Claude Fable; git and an authenticated gh CLI; a GitHub repository with Actions enabled; a sandboxed/disposable environment (see above).
CLAUDE.md Orchestrator charter — auto-loads every session
specs/
PROCESS.md the SDG process (never modified)
CLAUDE-PROCESS.md Claude Code bindings, protocols, phase runbook
PHILOSOPHY.md Liaison-only memory of Developer principles
GOALS.md non-negotiable goals (Developer-approved edits only)
tmp/ patches/ process working files
.claude/
settings.json model, effort, permissions defaults
agents/ sdg-reviewer, sdg-driver, sdg-engineer, sdg-specialist
prompts/ Liaison charter + per-phase mission prompts
sdg-bootstrap/ the bootstrap skill (not copied into projects)
MIT