skills.rest
JNZader
JNZaderCOMMUNITY
Explore all skills by this author →
GitHub

sdd-spec

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

Updated Mar 15, 2026
Search Tags:#specification#requirements#scenarios#orchestrator#delta-spec#change-proposal
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill sdd-spec-jnzader
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/JNZader/javi-ai/tree/main/delta/overrides/sdd-spec
Command: npx skills add https://github.com/JNZader/javi-ai --skill sdd-spec-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The sdd-spec skill automates the creation of structured delta specifications from change proposals, translating high-level ideas into concrete domain-specific requirements and scenarios.

Core Features & Use Cases

  • Produces delta-style documents (ADDED, MODIFIED, REMOVED) per domain with clear headers.
  • Consolidates multi-domain impacts into a single, coherent artifact and supports per-domain persistence strategies.
  • Integrates with orchestrator-driven workflows to ensure traceable, testable specs are generated from proposals.

Quick Start

Tell the orchestrator the change name and affected domains, and I will generate ready-to-persist delta specs.

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?▼

You can generate delta specifications by providing a change name and affected domains to the orchestrator, which then produces ADDED, MODIFIED, and REMOVED requirements with domain-specific scenarios for persistence.

What is a delta spec and when do I need it for requirements engineering?▼

A delta spec captures incremental requirement changes using ADDED, MODIFIED, and REMOVED classifications per domain. You need it when translating high-level change proposals into structured, traceable, and testable requirement artifacts.

How do I enforce RFC 2119 language in generated requirement scenarios?▼

To enforce RFC 2119 language in requirement scenarios, use a specification generation tool that automatically applies normative keywords like MUST and SHALL within the produced domain-specific scenarios and delta artifacts.

Can I use an orchestrator-driven workflow to produce multi-domain requirement changes?▼

Yes, you can use an orchestrator-driven workflow to consolidate multi-domain impacts from a change proposal into a single coherent artifact, supporting per-domain persistence strategies across engram, openspec, and hybrid modes.

What is the best way to structure added, modified, and removed requirements across multiple domains?▼

The best way to structure these requirements is to generate a delta-style document with clear headers per domain, consolidating multi-domain impacts into a single coherent artifact that supports per-domain persistence.

Does this specification generation approach support engram and openspec persistence modes?▼

Yes, this specification generation approach supports engram, openspec, and hybrid persistence modes to store the generated delta specifications and requirement artifacts within your chosen workflow infrastructure.

Related Skills

Explore More Software Engineering Skills→
adacosdevadacosdev

sdd-spec

Generate delta specifications for added, modified, or removed system behavior.

Community
Advanced
oteroweboteroweb

sdd-spec

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

Community
Advanced
kangarookingkangarooking
154

conversation-flow

Classify user intents and route conversations to specialized handlers.

Community
Advanced
mrp4stenmrp4sten
3

sdd-spec

Generate delta specifications in openspec format with RFC 2119 keywords.

Community
Advanced