sdd-mcp: Skill for Claude Code

SDD Custom Steering Document Creation

Create specialized steering documents that provide context-specific guidance beyond the standard product/tech/structure documents.

When to Use Custom Steering

Custom steering is useful for:

• Domain-specific rules: API design, database conventions
• File-type guidance: Test patterns, component standards
• Workflow processes: PR reviews, deployment procedures
• Team conventions: Code review standards, documentation rules

Inclusion Modes

Custom steering documents can be loaded in three ways:

Mode	Behavior	Use Case
ALWAYS	Loaded in every AI interaction	Core conventions, critical rules
CONDITIONAL	Loaded when file patterns match	Test-specific, API-specific rules
MANUAL	Referenced with @filename.md	Rarely needed, specialized contexts

Workflow

Step 1: Identify the Need

Ask yourself:

• What specialized context is missing?
• When should this guidance apply?
• Is this project-wide or context-specific?

Step 2: Choose Inclusion Mode

Is this guidance ALWAYS relevant?
├── YES → Use ALWAYS mode
│
└── NO → Is it relevant for specific file types?
         ├── YES → Use CONDITIONAL mode with patterns
         │         Examples: *.test.ts, src/api/**/*
         │
         └── NO → Use MANUAL mode
                  Reference with @filename.md when needed

Step 3: Create Document

Save to .spec/steering/{filename}.md:

# {Topic Name}

## Purpose
{Why this steering document exists}

## Scope
{When this guidance applies}

## Guidelines

### Guideline 1: {Name}
{Detailed guidance}

**Do:**
- {Good practice}

**Don't:**
- {Anti-pattern}

### Guideline 2: {Name}
{Detailed guidance}

## Examples

### Good Example
```{language}
{Code showing good practice}

Bad Example

// DON'T: {explanation}
{Code showing anti-pattern}

Checklist

• {Verification item 1}
• {Verification item 2}

---

Inclusion Mode: {ALWAYS | CONDITIONAL | MANUAL} File Patterns: {patterns for CONDITIONAL mode} Created: {date}