Slash Commands

A guide to SDD slash commands for Claude Code.

Overview

When you run sdd init, slash commands, development skills, and SDD workflow Skills 2.0 are automatically created in .claude/commands/ and .claude/skills/.

• 32 slash commands in .claude/commands/ — Korean, dot-notation (sdd.start, sdd.spec, …)
• 6 dev- skills* in .claude/skills/dev-*/ — existing development skills (dev-implement, dev-test, …)
• 32 sdd- Skills 2.0* in .claude/skills/sdd-*/ — English counterparts of each slash command (v1.6.0+)

Use --no-commands to skip slash command generation, or --no-skills to skip all skills (both dev-* and sdd-*).

Command List

Core Workflow

Command	Description
/sdd.start	Unified entry point
/sdd.constitution	Manage project principles
/sdd.spec	Create/modify feature specs (unified)
/sdd.plan	Create implementation plan
/sdd.tasks	Task breakdown
/sdd.prepare	Tool check
/sdd.implement	Sequential implementation
/sdd.validate	Spec validation

Note: /sdd.spec automatically determines whether you're writing a new feature or modifying an existing spec, and guides you to the appropriate workflow.

Domain & Reverse Engineering (v1.2.0)

Command	Description
/sdd.reverse	Reverse engineer specs from legacy code
/sdd.domain	Domain management (create, link, graph)
/sdd.context	Set working context

Development Skills (v1.2.0)

Note: Skills are different from slash commands. Claude automatically selects and uses them based on the work context.

Skill	Description
dev-implement	Spec-based TDD implementation
dev-next	Recommend next spec to implement
dev-review	Code review
dev-scaffold	Boilerplate generation
dev-status	Implementation progress
dev-test	Run Vitest tests

Skills 2.0 (v1.6.0+)

sdd init also generates 32 English Skills 2.0 under .claude/skills/sdd-*/SKILL.md. Each mirrors a slash command with a 1:1 kebab-case mapping (e.g., sdd.start → sdd-start).

Skills 2.0 include advanced frontmatter fields:

Field	Applied to
context: fork	7 analysis/domain skills (sdd-analyze, sdd-impact, sdd-sync, sdd-search, sdd-report, sdd-reverse, sdd-research)
context: manual-invoke-only	sdd-watch
disable-model-invocation: true	5 utility skills (sdd-guide, sdd-chat, sdd-cicd, sdd-watch, sdd-migrate)
allowed-tools	All sdd-* skills — minimum-privilege glob patterns (e.g., Bash(sdd validate*))

For details on Skills 2.0 frontmatter, see the Claude Code team's announcement.

Change Management

Command	Description
/sdd.impact	Change impact analysis
/sdd.transition	Switch between new <-> change workflows

Deprecated

Command	Replaced By	Description
/sdd.new	/sdd.spec	Create new feature spec
/sdd.change	/sdd.spec	Propose changes to existing spec

Analysis & Quality

Command	Description
/sdd.analyze	Analyze request and assess scope
/sdd.quality	Calculate spec quality score
/sdd.report	Generate project report
/sdd.search	Search specs
/sdd.status	Check project status
/sdd.list	List items
/sdd.sync	Validate spec-code synchronization
/sdd.diff	Visualize spec changes
/sdd.export	Export specs

Documentation Generation

Command	Description
/sdd.research	Technical research document
/sdd.data-model	Data model document
/sdd.guide	Workflow guide

Operations

Command	Description
/sdd.chat	Interactive SDD assistant
/sdd.watch	File watch mode
/sdd.migrate	Migrate from external tools
/sdd.cicd	CI/CD configuration
/sdd.prompt	Output prompts

Usage

Enter commands starting with a slash in Claude Code:

/sdd.start

When arguments are needed:

/sdd.spec user authentication feature

v1.2.0 New Features

Reverse Engineering Workflow

Automatically extract SDD specs from legacy code:

/sdd.reverse scan              # Scan project
/sdd.reverse extract           # Extract specs
/sdd.reverse review            # Review
/sdd.reverse finalize          # Finalize

Domain System

Logically group large projects:

/sdd.domain create auth        # Create domain
/sdd.domain graph              # Dependency graph
/sdd.context set auth payment  # Set working context

Development Skills

Support spec-based TDD development. Skills are automatically used by Claude based on the task (no / prefix):

• dev-next - Recommend next spec to implement
• dev-implement - Spec-based TDD implementation
• dev-test - Run tests
• dev-review - Code review

Example: "Implement the auth/login spec" -> Claude automatically uses the dev-implement skill