sdd-spec

Generate delta specifications for software changes under openspec/changes.

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-spec-tiagofur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/tiagofur/kakoclaw/tree/main/.claude/skills/sdd-spec
Command: npx skills add https://github.com/tiagofur/kakoclaw --skill sdd-spec-tiagofur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured approach to generate delta specifications for changes, enabling teams to describe added, modified, and removed behavior with consistent formats.

Core Features & Use Cases

  • Identify Affected Domains: Determine which spec domains are impacted by a proposal and group changes by domain.
  • Read Existing Specs: If openspec/specs/{domain}/spec.md exists, read to understand current behavior.
  • Write Delta Specs: Create delta specs under openspec/changes/{change-name}/ specs/ with ADDED/ MODIFIED/ REMOVED sections; or produce a full spec for new domains.
  • Return Summary: Generate a structured summary with specs created and coverage status.

Quick Start

Provide the delta specs for the change by following the delta-spec workflow and the templates in openspec.

Frequently Asked Questions about sdd-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate delta spec writing for software changes?▼

To automate delta spec writing for software changes, use this Skill to generate specifications detailing added, modified, and removed behaviors under openspec/changes for review. It standardizes descriptions by applying modular requirements and RFC 2119 language.

What is a delta specification in OpenSpec?▼

A delta specification in OpenSpec is a structured document defining added, modified, and removed behaviors for software changes. It enforces modular requirements and scenarios using RFC 2119 language to ensure testable and auditable documentation.

How do I generate specifications for modified and removed behaviors?▼

You generate specifications for modified and removed behaviors by applying the delta-spec workflow to create ADDED, MODIFIED, and REMOVED sections under openspec/changes. It reads existing specs to understand current behavior before writing the delta.

Does this approach work for changes across multiple spec domains?▼

Yes, this approach works for changes across multiple spec domains by identifying affected areas and grouping changes accordingly. It reads existing specs when present or produces a full spec for new domains to ensure comprehensive coverage.

Do I need existing OpenSpec files to document new software behaviors?▼

You do not need existing OpenSpec files to document new software behaviors. If openspec/specs/{domain}/spec.md is absent, the workflow produces a full specification for the new domain rather than a partial delta spec.