skills.rest
oteroweb
oterowebCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdd-spec

Generate structured delta specifications from change proposals using RFC 2119 keywords.

Updated Apr 2, 2026
Search Tags:#architecture#documentation#requirements#specifications#scenarios#delta-specs
One-click install
npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill sdd-spec-oteroweb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/oteroweb/OWFINANCE2026/tree/main/.claude/skills/sdd-spec
Command: npx skills add https://github.com/oteroweb/OWFINANCE2026 --skill sdd-spec-oteroweb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Write clear delta specifications by transforming change proposals into structured requirements and scenarios that describe what's ADDED, MODIFIED, or REMOVED from system behavior.

Core Features & Use Cases

  • Produces delta specs for changes across domains
  • Supports engram/openspec/hybrid persistence modes
  • Organizes changes by domain and prepares artifacts for review and implementation

Quick Start

Provide a change proposal to the orchestrator and trigger the spec-generation workflow to produce a delta specification for the affected domains.

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 from a change proposal?▼

To generate delta specifications, provide a change proposal to trigger the spec-generation workflow, which produces structured requirements and scenarios describing added, modified, or removed system behavior organized by domain.

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

A delta spec is a structured document capturing added, modified, or removed system behavior. You need one when transforming change proposals into clear requirements and scenarios for implementation and review.

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

Structure requirements and scenarios by applying RFC 2119 keywords within delta spec artifacts, ensuring formal scenario formatting and persistent rules across engram, openspec, hybrid, or none persistence modes.

Can I organize system change requirements across multiple domains?▼

Yes, you can organize system change requirements across multiple domains. The workflow categorizes added, modified, or removed behaviors by domain and prepares the resulting artifacts for review.

Does this approach support hybrid and openspec persistence modes?▼

Yes, this approach supports engram, openspec, hybrid, and none persistence modes. It formats delta specs with proper RFC 2119 keywords and scenario structures while satisfying the specific persistence rules of each mode.

What are the limitations of generating architecture documentation from change proposals?▼

Limitations include relying on the initial change proposal quality for accurate requirements generation. The delta spec process focuses on structural formatting and domain organization, requiring existing proposals to function correctly.

Related Skills

Explore More Software Engineering Skills→
thiagoooo34252thiagoooo34252
1

sdd-spec

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

Community
Intermediate
woutervanranstwoutervanranst
1

openspec-verify-change

Verify implementation alignment with delta specs, tasks, and design artifacts.

Community
Advanced
kryptobaseddevkryptobaseddev
160

ct-spec-writer

Generate RFC 2119 compliant specifications with structured templates and compliance criteria.

Community
Intermediate
mrp4stenmrp4sten
3

sdd-spec

Generate delta specifications in openspec format with RFC 2119 keywords.

Community
Advanced