sdd-spec

Transform change proposals into structured requirements and scenarios for delta specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write specifications with requirements and scenarios (delta specs for changes). Trigger: When the orchestrator launches you to write or update specs for a change.

Core Features & Use Cases

  • Generate delta specs for added, modified, and removed behaviors across one or more domains.
  • Produce structured requirements and scenarios that are testable and RFC 2119 compliant.
  • Support multiple persistence modes (engram, openspec, hybrid, none) and coordinate with the broader SDD workflow.

Quick Start

Provide the change name and affected domains, then let the orchestrator invoke the delta-spec writer to generate the specification.

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

Generate delta specifications by providing the change name and affected domains to an orchestrator. It transforms change proposals into structured, testable requirements and scenarios that document added, modified, and removed behaviors.

What are scenario-based specifications and when do I need them?

Scenario-based specifications document system behaviors through structured, testable requirements. You need them when writing delta specs for changes to ensure rigorous verification and clear tracking of added, modified, or removed behaviors across domains.

How do I document added, modified, and removed behaviors in requirements?

Document behavior changes by generating a delta specification that categorizes updates into added, modified, and removed requirements. This structured approach ensures all affected domains are clearly captured for scenario-based verification.

Does this specification writer support RFC 2119 compliant requirements?

Yes, the specification writer produces RFC 2119 compliant requirements. It structures change proposals into rigorous, testable requirements and scenarios that align with standard engineering compliance keywords.

Can I coordinate delta spec generation with an orchestrated change workflow?

Yes, delta spec generation supports orchestrated change workflows. The orchestrator launches the specification writer to generate or update specs based on the provided change name and affected domains.

What persistence modes are available for storing specifications?

Available persistence modes include engram, openspec, hybrid, and none. These modes allow you to store generated delta specifications and coordinate them within the broader specification-driven development workflow.