sdd-spec

Generate delta specifications with requirements and scenarios for system changes.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/EduardoJVN/my-ia-config --skill sdd-spec-eduardojvn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/EduardoJVN/my-ia-config/tree/main/.claude/skills/sdd-spec
Command: npx skills add https://github.com/EduardoJVN/my-ia-config --skill sdd-spec-eduardojvn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting changes to system specifications by generating delta specifications that clearly outline additions, modifications, and removals.

Core Features & Use Cases

  • Delta Specification Generation: Creates precise documentation for changes to requirements and scenarios.
  • Domain-Specific Specs: Organizes specifications by affected system domains (e.g., auth, payments).
  • Use Case: When a new feature is proposed, this Skill can automatically generate the updated specification document, highlighting exactly what needs to be added or changed from the existing requirements.

Quick Start

Use the sdd-spec skill to write delta specifications for the change described in proposal.md.

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 system changes?

Delta specifications document additions, modifications, and removals for system changes. This skill generates them by identifying affected domains, reading current specs, and writing structured spec files with requirements and scenarios based on your proposals.

What is a delta spec and when do I need one for requirements documentation?

A delta spec outlines precise changes to requirements and scenarios for a system. You need one when a new feature is proposed or existing documentation requires updates, allowing you to highlight exactly what must be added or changed from current specs.

How do I generate testable requirements using Given/When/Then scenario structures?

Generate testable requirements by writing scenario structures using Given/When/Then syntax alongside RFC 2119 keywords. This skill formats delta specifications to ensure clear, testable documentation for system changes across affected domains.

Can I organize specifications by affected system domains like auth or payments?

Yes, organizing specifications by affected system domains like auth or payments is supported. The skill identifies affected domains from your proposals and writes new or modified spec files structured accordingly to maintain clear domain-specific documentation.

Do I need existing documentation to generate a delta spec for a feature proposal?

Existing documentation is read to identify current requirements and generate accurate delta specs. The skill reads current spec files to determine exactly what needs to be added or modified, ensuring new documentation builds directly upon your established baseline.

What is the best way to document changes to existing requirements and scenarios?

The best way to document changes is generating delta specifications that clearly outline additions, modifications, and removals. This skill automates reading current specs and writing modified spec files in a structured format with RFC 2119 keyword adherence.