skills.rest
aroca89
aroca89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

sdd-spec

Generate delta specifications for SDD change proposals with RFC 2119 requirements.

Updated Apr 8, 2026
Search Tags:#sdd#orchestrator#openspec#delta-specs#requirements-engineering#scenario-writing#engram
One-click install
npx skills add https://github.com/aroca89/roca_teams --skill sdd-spec-aroca89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/aroca89/roca_teams/tree/main/skills/sdd-spec
Command: npx skills add https://github.com/aroca89/roca_teams --skill sdd-spec-aroca89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It keeps Spec-Driven Development changes aligned by turning proposals into structured delta specifications so that each orchestrated phase understands what requirements are added, modified, or removed before implementation begins.

Core Features & Use Cases

  • Delta requirement drafting: Author added, modified, and removed requirements with RFC 2119 language and Given/When/Then scenarios for every change.
  • Multi-domain coverage: Aggregate affected domains, compare against existing specs, and split new domains into full specifications when no prior behavior exists.
  • Persistence compliance: Respect engram, openspec, and hybrid storage conventions so the orchestrator can persist and retrieve specs without breaking the workflow.
  • Use Case: When a new invoicing feature is proposed, use this skill to produce the spec artifact that the design and implementation phases rely on.

Quick Start

Ask the orchestrator to run sdd-spec for the current change so it can craft delta requirements from the proposal.

Frequently Asked Questions about sdd-spec

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

FAQPage Schema
How do I structure delta specifications for Spec-Driven Development change proposals?▼

Delta specifications for SDD change proposals are structured by defining added, modified, and removed requirements using RFC 2119 language and Given-When-Then scenarios. This ensures every orchestrated phase understands the exact scope changes before implementation begins.

What is the best way to author requirements with Given-When-Then scenarios for new features?▼

Authoring requirements with Given-When-Then scenarios involves drafting delta specifications that classify changes as added, modified, or removed. This method applies RFC 2119 requirement strength to ensure each scenario is verifiable and aligned with the proposed feature scope.

How does delta specification generation handle new domains with no prior existing specs?▼

When no prior behavior exists for a new domain, delta specification generation splits the new domain into a full specification rather than a delta. This multi-domain coverage aggregates affected domains and compares them against existing specs to maintain consistency.

Can I use engram and openspec storage conventions for orchestrator-driven spec persistence?▼

Yes, orchestrator-driven spec persistence supports engram, openspec, and hybrid storage conventions. This compliance ensures the orchestrator can seamlessly persist and retrieve structured requirements without breaking the existing workflow.

How do I keep RFC 2119 requirement strength consistent across design and verification phases?▼

RFC 2119 requirement strength is kept consistent across design and verification phases by generating delta specifications that the orchestrator applies uniformly. This structured approach ensures all downstream phases rely on the same requirement definitions.

Do I need an orchestrator to run sdd-spec for my current change proposal?▼

Yes, you need an orchestrator to run the spec generation process. You ask the orchestrator to execute the task for your current change so it can craft the delta requirements directly from the proposal input.

Related Skills

Explore More Software Engineering Skills→
adacosdevadacosdev

sdd-spec

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

Community
Advanced
ajrmooreukajrmooreuk

pfc-delta-evaluate

Score current state, define future state, and quantify delta across CGA dimensions.

Community
Advanced
kurojskurojs
2

sdd-verify

Validate SDD changes against specifications and designs with test evidence.

Community
Advanced
thiagoooo34252thiagoooo34252
1

sdd-spec

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

Community
Intermediate