sdd-spec

Generate delta specifications with structured requirements and scenarios from change proposals.

Updated Apr 1, 2026

Search Tags:#specification #requirements #scenarios #openspec #delta-spec #engram #change-proposal

Ready to run

npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-spec-maxculen86

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/maxculen86/coding-bro-ai/tree/main/internal/assets/skills/sdd-spec
Command: npx skills add https://github.com/maxculen86/coding-bro-ai --skill sdd-spec-maxculen86

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writes delta specifications for change proposals by turning proposals into structured requirements and scenarios, enabling precise tracking of additions, modifications, and removals.

Core Features & Use Cases

Generates delta specs per domain and capability based on the proposal.
Produces complete requirement blocks and scenarios suitable for verification and testing.
Supports multiple persistence modes (engram, openspec, hybrid, none) and produces a spec artifact at sdd/{change-name}/spec.

Quick Start

Run this skill with a change proposal to generate delta specifications and supporting scenarios.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema

How do I generate delta specifications for a change proposal?▼

Delta specifications are generated by translating a change proposal into structured requirements and scenarios, tracking additions, modifications, and removals. Each requirement receives at least one scenario and uses RFC 2119 keywords for precise verification.

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

A delta spec captures structured requirements and scenarios for proposed changes, enabling precise tracking of additions, modifications, and removals. It is needed when transforming proposals into testable verification artifacts.

Does this approach support openspec and engram persistence modes?▼

Yes, it supports openspec, engram, hybrid, and none persistence modes. These conventions determine whether specs are stored on-disk or kept memory-only, with final artifacts persisted under sdd/{change-name}/spec.

How do I write requirements and scenarios using RFC 2119 keywords?▼

Requirements are written as structured blocks where each one must have at least one scenario, utilizing RFC 2119 keywords for normative language. This ensures the generated delta specs are suitable for verification and testing.

What are the limitations of memory-only delta specs?▼

Using the none persistence mode keeps delta specs in memory only, meaning no on-disk artifact is persisted under sdd/{change-name}/spec. This limits tracking and retrieval compared to openspec or engram modes.