skills.rest
adacosdev
adacosdevCOMMUNITY
Explore all skills by this author →
Website𝕏@aacosa34GitHub

sdd-spec

Generate delta specifications for added, modified, or removed system behavior.

Updated Feb 1, 2026
Search Tags:#requirements#specifications#orchestration#engineering#scenarios#multi-domain#delta-specs
One-click install
npx skills add https://github.com/adacosdev/dotfiles --skill sdd-spec-adacosdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/adacosdev/dotfiles/tree/main/dot_config/opencode/skills/sdd-spec
Command: npx skills add https://github.com/adacosdev/dotfiles --skill sdd-spec-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes delta specifications describing added, modified, or removed system behavior based on a change proposal.

Core Features & Use Cases

  • Generates delta specs for added, modified, or removed requirements and scenarios across multiple domains.
  • Follows a structured orchestration workflow: identify affected domains, read existing specs, draft delta specs, and persist artifacts according to the selected mode.
  • Supports multiple persistence backends (Engram, OpenSpec, Hybrid) with upsert semantics and domain headers when needed.

Quick Start

Draft the initial delta specs by supplying the change name and the artifact store mode.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
How do I write delta specifications for added or modified system behavior?▼

Delta specifications describe added, modified, or removed system behavior by supplying a change name and artifact store mode to generate domain-specific spec artifacts with persistence rules.

What is the best way to coordinate delta spec generation across multiple engineering domains?▼

Multi-domain delta spec generation follows a structured orchestration workflow that identifies affected domains, reads existing specs, drafts delta specs, and persists artifacts according to the selected mode.

Can I persist delta specs across different artifact store backends?▼

Delta specs support multiple persistence backends including Engram, OpenSpec, and Hybrid modes, applying upsert semantics and domain headers when needed to enforce persistence contract rules.

How do I draft full specs with domain headers instead of just delta specs?▼

Full specs with domain headers are produced by configuring the artifact-store mode to output full specifications, enforcing persistence contracts while maintaining domain-specific formatting rules.

When should I use delta specs instead of full specifications for change proposals?▼

Delta specs are used when describing specific added, modified, or removed requirements and scenarios from a change proposal, whereas full specs provide complete domain-level specification snapshots.

Does delta spec generation require existing specifications to read from?▼

The orchestration workflow reads existing specs across affected domains to draft accurate delta specifications, ensuring proposed changes are properly contextualized against current system behavior.

Related Skills

Explore More Software Engineering Skills→
fwdarthfwdarth

sdd-propose

Generate structured Markdown change proposals with intent, scope, and risks.

Community
Intermediate
anton-abyzovanton-abyzov
156

spec-kit-expert

Generate RFC 2119-compliant specifications with Gherkin scenarios and user stories.

Community
Basic
HerbertGaoHerbertGao
1

openspec-new-change

Bootstrap a new OpenSpec change with a structured workflow.

Community
Advanced
optionioptioni

openspec-sync-specs

Sync delta specifications into main specifications using the openspec CLI.

Official
Intermediate