skills.rest
RamonsDka
RamonsDkaCOMMUNITY
Explore all skills by this author →
GitHub

sdd-spec

Generate delta specs with ADDED, MODIFIED, and REMOVED sections by domain.

1|1|Updated Apr 19, 2026
Search Tags:#specification#requirements#scenarios#openspec#change-management#delta-spec
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-spec-ramonsdka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/sdd-spec
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill sdd-spec-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write delta specs describing what is ADDED, MODIFIED, or REMOVED from a proposal, turning vague ideas into concrete, testable requirements and scenarios.

Core Features & Use Cases

  • Generate delta specs with clear ADDED, MODIFIED, and REMOVED sections for each domain.
  • Group changes by domain and produce structured, executable scenarios using Given/When/Then.
  • Enforce RFC 2119 keywords and compact narrative to keep specs under the artifact size limit.

Quick Start

Provide a change proposal and allow me to generate delta specs covering added, modified, or removed behaviors.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
How do I write a delta spec for system changes?▼

Organize system changes by domain and produce structured scenarios using Given/When/Then formats. These executable scenarios compactly describe the exact behavior modifications tested within a strict artifact size limit.

When do I need to use RFC 2119 keywords in requirements specifications?▼

Use RFC 2119 keywords in requirements specifications to enforce strict conformance levels when defining delta specs. This ensures precise, unambiguous language for what is ADDED, MODIFIED, or REMOVED from the system's behavior.

Can I document cross-domain changes in a single specification artifact?▼

Yes, you can document cross-domain changes in a single specification artifact. The delta spec process groups changes by domain and produces structured requirements and scenarios, keeping the total artifact compact and under 650 words.

What is the best way to structure testable scenarios for change management?▼

The best way to structure testable scenarios for change management is using compact 3-5 line Given/When/Then narratives. This enforces clear executable conditions while keeping the overall delta spec within size limits.

Are there limitations to the size of a delta spec artifact?▼

Yes, delta spec artifacts are limited to 650 words. The specification process enforces compact 3-5 line scenarios and concise narratives to ensure the generated requirements and scenarios strictly adhere to this artifact size constraint.

Related Skills

Explore More Software Engineering Skills→
MarcialFantiniMarcialFantini

sdd-spec

Generate delta specs documenting added, modified, and removed requirements with RFC 2119 keywords.

Community
Advanced
NSObjectsNSObjects
4

specifying

Define behavioral requirements with GIVEN/WHEN/THEN scenarios and edge cases.

Community
Advanced
memorysavermemorysaver

openspec-sync-specs

Merge delta specs under openspec/changes into main specs.

Community
Intermediate
finger-gunfinger-gun
4

openspec-sync-specs

Merge delta specifications into main OpenSpec specs with intelligent changes.

Official
Advanced