dominicode-sdd-creator

bezael/sdd-creator — Dominicode Skills

🇪🇸 Versión en español

Generates specs following the Spec-Driven Development methodology, as adapted by Dominicode (Bezael Pérez), in any AI agent: Claude, Codex, Gemini, Cursor, Aider, Continue.

Before generating code, the agent produces spec.md (6 sections), plan.md (technical decisions) and tasks.md (TDD-ordered task list) under specs/<feature-slug>/.

It first grounds the spec in your existing project (stack, conventions, prior specs), keeps a versioned specs/INDEX.md as project memory, and verifies every feature traces to a task before hand-off — all in plain Markdown, zero dependencies.

---

Skills catalog

Engineering

Skill	Description
dominicode-sdd-creator	Spec-Driven Development — grounds the spec in your project, writes spec/plan/tasks before code, and keeps a specs/INDEX.md project memory.

---

Quick install (recommended)

npx skills@latest add bezael/sdd-creator

The CLI asks which skills to install and for which agents (Claude Code, Cursor, Codex, etc.) and configures everything automatically.

---

Manual install (per-agent fallback)

Claude Code (Anthropic)

Option A — Global skill (recommended):

# Copy the skill to your personal skills directory
cp -r skills/engineering/dominicode-sdd-creator ~/.claude/skills/

# Verify
ls ~/.claude/skills/dominicode-sdd-creator/SKILL.md

From that point on, every Claude Code session will have the skill available.

Option B — Per-project skill:

mkdir -p .claude/skills
cp -r skills/engineering/dominicode-sdd-creator .claude/skills/

Claude.ai (web/desktop)

1. Bundle the skill: zip -r dominicode-sdd-creator.skill skills/engineering/dominicode-sdd-creator/
2. In Claude.ai → Settings → Skills → Upload skill → select the .skill file.

Codex CLI (OpenAI)

# In the project root
cp skills/engineering/dominicode-sdd-creator/AGENTS.md ./AGENTS.md
cp -r skills/engineering/dominicode-sdd-creator/templates ./templates
cp -r skills/engineering/dominicode-sdd-creator/references ./references

Cursor

mkdir -p .cursor/rules
cp skills/engineering/dominicode-sdd-creator/AGENTS.md .cursor/rules/dominicode-sdd-creator.mdc
cp -r skills/engineering/dominicode-sdd-creator/templates ./templates
cp -r skills/engineering/dominicode-sdd-creator/references ./references

Add the Cursor frontmatter at the top of the .mdc file:

---
description: Dominicode SDD Creator — write spec before code
alwaysApply: true
---

Gemini CLI (Google)

cp skills/engineering/dominicode-sdd-creator/AGENTS.md ./GEMINI.md
cp -r skills/engineering/dominicode-sdd-creator/templates ./templates
cp -r skills/engineering/dominicode-sdd-creator/references ./references

Aider, Continue and other AGENTS.md-compatible tools

Copy AGENTS.md to the project root together with templates/ and references/.

Agents without instruction-file support

Paste the contents of AGENTS.md at the beginning of your system prompt.

---

Repo structure

bezael/sdd-creator
├── .claude-plugin/
│   └── plugin.json               ← read by the npx skills CLI and Claude Code
├── skills/
│   └── engineering/
│       ├── README.md
│       └── dominicode-sdd-creator/
│           ├── SKILL.md           ← Claude Code
│           ├── AGENTS.md          ← other agents
│           ├── templates/
│           │   ├── spec.md
│           │   ├── plan.md
│           │   ├── tasks.md
│           │   ├── implementation.md
│           │   └── specs-index.md
│           └── references/
│               ├── examples.md
│               ├── codebase-inspection.md
│               ├── tdd-workflow.md
│               ├── test-runner-detection.md
│               └── traceability.md
├── CLAUDE.md
├── LICENSE
└── README.md

---

How to use

Once installed, describe what you want to build:

"I want to build an app for freelancers to manage invoices"
"let's create a metrics dashboard for my store"
"design an authentication feature with magic links"

The agent will:

1. Detect the context level (high / medium / low)
2. Ground the spec in your project — detect the stack in use, conventions and prior specs (a "Project Context Snapshot")
3. Interview you or produce a draft accordingly
4. Generate specs/<feature>/spec.md with the 6 sections
5. After your confirmation, generate plan.md
6. After your confirmation, generate tasks.md with TDD — including a coverage matrix so no feature is left without a task
7. Record the spec in specs/INDEX.md (project memory) and reuse its shared decisions next time
8. Only then start coding, task by task

---

Philosophy

Spec → Plan → Tests → Code. Code is the last thing that happens, not the first.

The Dominicode adaptation of SDD is documented in the book and in Dominicode courses: