
Spec Driven Dev
- 1 repo stars
- Updated June 29, 2026
- dorg-atsabari/forge
A full product-dev pipeline for Claude Code: use cases, tech design, UX/UI design, dev plans, pre-commit checks, and commit workflows.
About
spec-driven-dev is a Claude Code skill in the Design & UI/UX category. A full product-dev pipeline for Claude Code: use cases, tech design, UX/UI design, dev plans, pre-commit checks, and commit workflows.
- spec-driven-dev
- Design & UI/UX
- AI-coding skill
Spec Driven Dev by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add dorg-atsabari/forge/plugin install spec-driven-dev@forgeAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | June 29, 2026 |
| Repository | dorg-atsabari/forge ↗ |
What it does
A full product-dev pipeline for Claude Code: use cases, tech design, UX/UI design, dev plans, pre-commit checks, and commit workflows.
README.md
spec-driven-dev
A Claude Code plugin that provides a full product-development pipeline — from raw requirements all the way to shipped code.
What's inside
Skills
| Skill | Purpose |
|---|---|
use-cases-generator |
Extract structured use cases from raw requirements |
tech-design-generator |
Produce technical architecture designs (components, APIs, data flows) |
ui-ux-design-generator |
Two-phase UX + UI design with interactive HTML previews and briefs |
create-implementation-order |
Analyze specs and propose a domain-grouped implementation order |
dev-plan |
Break work into minimal, independently committable implementation steps |
end-to-end |
Run the full pipeline end-to-end |
document |
Align documentation with the current codebase |
pre-commit |
Run quality gates (tests, build) before committing |
commit |
Analyze staged changes and craft a conventional commit |
Rules
Generic rules the skills rely on. They live in rules/ and are included for reference — Claude Code plugins don't auto-load rules, so consumers should wire them into their own project (see Install).
| Rule | What it enforces |
|---|---|
context-source-of-truth |
The codebase is the primary source of truth. Trust code over docs; verify before designing from docs |
documentation-workflow |
Dev and docs are separate workflows. Specs stay in specs/ until /document syncs them |
Install
Add the marketplace, then install the plugin:
/plugin marketplace add https://github.com/dorg-atsabari/forge
/plugin install spec-driven-dev@forge
After installing, skills are available as /spec-driven-dev:<skill> (e.g., /spec-driven-dev:commit).
Wire up the rules (optional but recommended)
Rules aren't auto-loaded by installed plugins — they ship in the plugin folder as reference. To enforce them in your project, copy them into your project's .claude/rules/:
mkdir -p .claude/rules
cp <plugin-location>/rules/*.md .claude/rules/
Claude Code auto-loads everything in .claude/rules/ into every session. No CLAUDE.md wiring needed.
Typical flow
requirements → /use-cases-generator
→ /tech-design-generator
→ /ui-ux-design-generator
→ /create-implementation-order
→ /dev-plan → implement → /pre-commit → /commit → /document
License
MIT