sdd-spec

Generate structured delta specifications with Given/When/Then scenarios from change proposals.

2|Updated Jul 29, 2025
One-click install
npx skills add https://github.com/kurojs/EnderDots --skill sdd-spec-kurojs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/kurojs/EnderDots/tree/main/.config/opencode/skills/sdd-spec
Command: npx skills add https://github.com/kurojs/EnderDots --skill sdd-spec-kurojs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a proposed product/system change into precise, testable delta specifications so teams can align on what must change, what must be removed, and what new scenarios must be supported.

Core Features & Use Cases

  • Delta spec authoring for modified capabilities: Creates updated requirement blocks that fully replace existing behavior descriptions, preventing scenario loss during archiving.
  • Full spec authoring for new capabilities: Produces complete specifications for newly introduced capabilities when no prior spec exists.
  • Persistence-aware outputs: Supports multiple artifact persistence modes (engram, openspec, hybrid, none) to fit different orchestration pipelines.

Quick Start

Ask the AI orchestrator to delegate spec work for the change so this skill outputs the correct delta or full capability specifications based on the proposal’s Capabilities section.

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 change management proposals?

Delta specifications map new and modified capabilities into requirement and scenario documents by fully replacing existing behavior descriptions to prevent scenario loss during archiving. This ensures teams align on what must change or be removed with testable Given/When/Then scenarios.

What is the best way to structure requirements using RFC 2119 for system changes?

Requirements using RFC 2119 apply standardized strength levels like MUST or SHOULD to define modified capabilities, ensuring precise and testable delta specifications. This enforces clear compliance expectations within the generated scenario documents.

How do I generate testable Given/When/Then scenarios for a new capability spec?

Generating testable Given/When/Then scenarios for a new capability produces a complete specification document when no prior spec exists. It maps the proposed behavior into structured requirement blocks to ensure full test coverage.

Does this spec authoring process support different artifact persistence modes?

Yes, spec authoring supports multiple persistence modes including engram, openspec, hybrid, and none. This persistence-aware output ensures the generated delta specifications fit seamlessly into different orchestration pipelines.

When do I need to update existing requirements versus creating a full new spec?

You update existing requirements when modifying a current capability, creating delta specifications that fully replace prior behavior descriptions. You create a full new spec only when introducing a completely new capability with no existing baseline.

Why do modified capability requirements fully replace existing behavior descriptions?

Modified capability requirements fully replace existing behavior descriptions to prevent scenario loss when the old spec is archived. This ensures no critical test scenarios are dropped during the change management update process.