sdd-spec

Generate delta specifications with added, modified, and removed requirements.

10|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-spec-alan-thegentleman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/Alan-TheGentleman/gentle-ai-enterprise/tree/main/skills/sdd-spec
Command: npx skills add https://github.com/Alan-TheGentleman/gentle-ai-enterprise --skill sdd-spec-alan-thegentleman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta specifications translate proposals into structured requirements and scenarios, enabling teams to track changes with clarity and consistency.

Core Features & Use Cases

  • Generate added, modified, and removed requirements as delta specs
  • Group changes by domain and re-use existing specs when available
  • Produce either delta specs or full specs for new domains, with a clear artifact plan

Quick Start

Provide delta specs for the latest change proposal to document added, modified, and removed requirements.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
How do I document added, modified, and removed requirements for a change proposal?

To document requirements for a change proposal, you generate delta specifications that encode added, modified, and removed requirements. This structured approach translates proposals into clear requirements and scenarios, enabling consistent change tracking across your engineering domains.

What is a delta specification in engineering change management?

A delta specification is a structured artifact that translates a change proposal into added, modified, and removed requirements. It enables engineering teams to track changes with clarity and consistency by segmenting updates into specific domains rather than rewriting entire specifications.

How do I group requirements changes by domain and reuse existing specs?

You group requirements by applying domain segmentation to the change proposal, which allows you to reuse existing specs when available. This process produces a structured artifact plan containing per-domain content and a summary of the changes made.

When do I need to generate a full spec instead of a delta spec for a new domain?

You need to generate a full spec instead of a delta spec when you are introducing a completely new domain. This approach ensures you establish a complete baseline of requirements, whereas delta specs are reserved for modifying existing domains with added, changed, or removed requirements.

How do I produce a structured artifact plan for domain-specific requirements?

You produce a structured artifact plan by conforming to configured persistence conventions while generating the delta structure. The resulting plan includes per-domain content and a comprehensive summary of all added, modified, and removed requirements.