How do I install the Sdd skill?

Run npx skillmds@latest add meleantonio/sdd in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sdd?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

meleantonio (@meleantonio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sdd by meleantonio — Agent Skill

Name: Sdd
Author: meleantonio

Sdd

Implements the Spec-Driven Development lifecycle (Intent, Requirements, Design, Tasks, Build) for structured feature development. Use when the user wants to scaffold a new feature spec, generate EARS requirements, create a technical design, break work into tasks, or check spec status. Trigger on keywords: sdd, spec-driven, ears requirements, feature spec.

meleantonio 1b2b0ad 6 files · 9.7 KB Updated Sep 17, 2026

File contents

Spec-Driven Development (SDD)

Core Philosophy

Clarity before Code: Never generate code until requirements and design are approved.
Iterative Refinement: Loop through Req → Design → Tasks until solid.
Code via Docs: The truth is in the markdown files, not the chat.

Commands

Execute in the project root (where spec/ and steering/ live).

`init`

Scaffold the SDD folder structure and template files.

If spec/ already exists, skip or ask before overwriting.
Create spec/ and steering/.
Create spec/intent.md (blank or minimal placeholder).
Copy templates from .cursor/skills/sdd/templates/ into the project:
- templates/spec/requirements.md → spec/requirements.md
- templates/spec/design.md → spec/design.md
- templates/spec/tasks.md → spec/tasks.md
- templates/steering/coding-standards.md → steering/coding-standards.md

`reqs`

Generate EARS requirements from intent.

Read spec/intent.md and steering/*.md.
Convert the intent into EARS requirements (see EARS Quick Reference below). Add a Properties (invariants) section.
Write to spec/requirements.md.
Ask for user approval before proceeding.

`design`

Generate technical design from requirements.

Read spec/requirements.md and steering/*.md.
Create a technical design: architecture, data models, component interfaces, error handling, security. Apply the Design Checklist below.
Write to spec/design.md.
Ask for user approval before proceeding.

`tasks`

Generate implementation tasks from design.

Read spec/design.md and spec/requirements.md.
Create a sequential task list: max two levels (Task > Subtask). Link each task to requirement IDs (e.g. REQ-001). Follow Task Rules below.
Write to spec/tasks.md.
Ask for user approval before proceeding.

`status`

Report current state of the spec.

List files in spec/ (and optionally steering/).
If spec/tasks.md exists, count unchecked [ ] vs checked [x] and summarize.

EARS Quick Reference

Ubiquitous: <system> shall <response>
Event-Driven: WHEN <trigger> [precondition] the <system> shall <response>
Unwanted: IF <unwanted condition> THEN the <system> shall <response>
State-Driven: WHILE <system state>, the <system> shall <response>
Optional: WHERE <feature is included>, the <system> shall <response>

Use IDs like [REQ-001]; add a Properties (Invariants) section for universal correctness statements.

Design Checklist

Edit ruthlessly (remove over-engineering).
Check for circular dependencies; fix via interface extraction, layering, or events.
Ensure alignment with steering documents.

Task Rules

Two-level hierarchy maximum (Task > Subtask).
Sequential order (each task builds on previous).
Traceability: each task or subtask links back to requirement IDs (e.g. Traceability: Implements REQ-001).

Additional Resources

For full framework detail (workflow, refinement, iteration triggers), see reference.md.

---name: sdddescription: Implements the Spec-Driven Development lifecycle (Intent, Requirements, Design, Tasks, Build) for structured feature development. Use when the user wants to scaffold a new feature spec, generate EARS requirements, create a technical design, break work into tasks, or check spec status. Trigger on keywords: sdd, spec-driven, ears requirements, feature spec.---# Spec-Driven Development (SDD)## Core Philosophy1. **Clarity before Code:** Never generate code until requirements and design are approved.2. **Iterative Refinement:** Loop through Req → Design → Tasks until solid.3. **Code via Docs:** The truth is in the markdown files, not the chat.## CommandsExecute in the **project root** (where `spec/` and `steering/` live).### `init`Scaffold the SDD folder structure and template files.1. If `spec/` already exists, skip or ask before overwriting.2. Create `spec/` and `steering/`.3. Create `spec/intent.md` (blank or minimal placeholder).4. Copy templates from `.cursor/skills/sdd/templates/` into the project: - `templates/spec/requirements.md` → `spec/requirements.md` - `templates/spec/design.md` → `spec/design.md` - `templates/spec/tasks.md` → `spec/tasks.md` - `templates/steering/coding-standards.md` → `steering/coding-standards.md`### `reqs`Generate EARS requirements from intent.1. Read `spec/intent.md` and `steering/*.md`.2. Convert the intent into EARS requirements (see EARS Quick Reference below). Add a Properties (invariants) section.3. Write to `spec/requirements.md`.4. Ask for user approval before proceeding.### `design`Generate technical design from requirements.1. Read `spec/requirements.md` and `steering/*.md`.2. Create a technical design: architecture, data models, component interfaces, error handling, security. Apply the Design Checklist below.3. Write to `spec/design.md`.4. Ask for user approval before proceeding.### `tasks`Generate implementation tasks from design.1. Read `spec/design.md` and `spec/requirements.md`.2. Create a sequential task list: max two levels (Task > Subtask). Link each task to requirement IDs (e.g. `REQ-001`). Follow Task Rules below.3. Write to `spec/tasks.md`.4. Ask for user approval before proceeding.### `status`Report current state of the spec.1. List files in `spec/` (and optionally `steering/`).2. If `spec/tasks.md` exists, count unchecked `[ ]` vs checked `[x]` and summarize.## EARS Quick Reference- **Ubiquitous:** `<system> shall <response>`- **Event-Driven:** `WHEN <trigger> [precondition] the <system> shall <response>`- **Unwanted:** `IF <unwanted condition> THEN the <system> shall <response>`- **State-Driven:** `WHILE <system state>, the <system> shall <response>`- **Optional:** `WHERE <feature is included>, the <system> shall <response>`Use IDs like `[REQ-001]`; add a **Properties (Invariants)** section for universal correctness statements.## Design Checklist- Edit ruthlessly (remove over-engineering).- Check for circular dependencies; fix via interface extraction, layering, or events.- Ensure alignment with steering documents.## Task Rules- Two-level hierarchy maximum (Task > Subtask).- Sequential order (each task builds on previous).- Traceability: each task or subtask links back to requirement IDs (e.g. *Traceability:* Implements `REQ-001`).## Additional Resources- For full framework detail (workflow, refinement, iteration triggers), see [reference.md](reference.md).

Frequently asked questions

Sdd

File contents

Spec-Driven Development (SDD)

Core Philosophy

Commands

init

reqs

design

tasks

status