sdd-spec

Generate delta specifications detailing added, modified, and removed requirements and scenarios.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/josemartinrodriguezmortaloni/opencode-config --skill sdd-spec-josemartinrodriguezmortaloni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/josemartinrodriguezmortaloni/opencode-config/tree/main/skill/sdd-spec
Command: npx skills add https://github.com/josemartinrodriguezmortaloni/opencode-config --skill sdd-spec-josemartinrodriguezmortaloni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting changes to software by generating precise delta specifications, ensuring clarity and consistency in requirements.

Core Features & Use Cases

  • Delta Specification Generation: Creates ADDED, MODIFIED, and REMOVED requirements and scenarios for specific domains.
  • Full Specification Generation: Writes complete specifications for new domains.
  • Use Case: When a new feature is proposed, this Skill can automatically generate the detailed requirements and testable scenarios needed for development, based on the proposal and existing documentation.

Quick Start

Use the sdd-spec skill to write delta specs for the 'user-auth-update' change.

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 specs for software changes?

To write delta specs, analyze existing proposals and project configurations to generate structured ADDED, MODIFIED, and REMOVED requirements and scenarios for specific domains. This ensures clarity and consistency when documenting software changes.

What is a delta specification in spec-driven development?

A delta specification in spec-driven development details the exact ADDED, MODIFIED, and REMOVED requirements and scenarios for a system change. It transforms proposals into structured, actionable documentation for new or existing behaviors.

When do I need to generate full specifications instead of delta specs?

Generate full specifications when establishing an entirely new domain rather than modifying an existing one. Delta specs are used specifically for detailing changes to current system behaviors, while full specs document complete foundational requirements.

Can I use scenario writing to document modified requirements for an existing domain?

Yes, scenario writing is used to document modified requirements by analyzing proposals against existing specs. This generates structured, testable scenarios that define how specific domain behaviors change during software updates.

What is the best way to structure requirements for a new system behavior?

The best way to structure requirements is by transforming proposals into structured, actionable documentation using defined formats and persistence contracts. This categorizes changes into ADDED, MODIFIED, and REMOVED requirements and scenarios.

Do I need existing specs to generate delta specifications for software changes?

Yes, generating delta specifications requires analyzing existing specs and project configurations alongside proposals. This comparison allows the system to accurately identify and document ADDED, MODIFIED, and REMOVED requirements.