skills.rest
Strocs
StrocsCOMMUNITY
Explore all skills by this author →
Website𝕏@_StrocsGitHub

sdd-spec

Write delta specifications with ADDED, MODIFIED, and REMOVED requirements and scenarios.

Updated Nov 19, 2024
Search Tags:#specification#requirements#openspec#given-when-then#rfc2119#delta-spec
One-click install
npx skills add https://github.com/Strocs/.dotfiles --skill sdd-spec-strocs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/Strocs/.dotfiles/tree/main/.config/opencode/skills/sdd-spec
Command: npx skills add https://github.com/Strocs/.dotfiles --skill sdd-spec-strocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts change proposals into structured delta specifications that state what is ADDED, MODIFIED, or REMOVED so teams have clear, testable requirements and scenarios for implementation.

Core Features & Use Cases

  • Delta Specifications: Produce ADDED, MODIFIED, and REMOVED requirement sections with RFC 2119 strength and Given/When/Then scenarios.
  • Mode-aware Persistence: Respect artifact store modes (engram, openspec, none) and follow the repository's persistence and openspec conventions.
  • Handoff-ready Output: Create domain-grouped spec files under openspec/changes/{change-name}/specs/{domain}/spec.md and return an executive summary and structured envelope for the orchestrator.

Quick Start

Use the sdd-spec skill to generate delta specifications for the change proposal 'add-recurring-payments', grouping requirements by domain and including at least one happy-path and one edge-case scenario.

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 proposed system changes?▼

Delta specifications for proposed changes are written as ADDED, MODIFIED, and REMOVED requirements using RFC 2119 strength and Given/When/Then scenarios, grouped by domain. This produces testable requirement artifacts for implementation.

What is a delta spec and when do I need one for my project?▼

A delta spec states exactly what requirements are ADDED, MODIFIED, or REMOVED for a proposed change. You need one to give teams clear, testable requirements and scenarios before implementation begins.

How do I generate Given/When/Then scenarios grouped by domain?▼

To generate Given/When/Then scenarios grouped by domain, apply the change proposal across software domains like auth or payments, producing domain-grouped spec files under openspec/changes with happy-path and edge-case scenarios.

Does the delta spec output work with openspec and engram artifact stores?▼

Yes, delta spec generation respects artifact store modes including engram, openspec, and none. It follows the repository's persistence and openspec conventions to create handoff-ready spec files.

Can I produce full specifications instead of deltas for new domains?▼

Yes, when the change proposal introduces new domains, the process produces full specifications instead of delta specs. For existing domains, it generates ADDED, MODIFIED, and REMOVED requirement sections.

What limitations exist when generating requirements with RFC 2119 strength?▼

The specification generation follows RFC 2119 requirement strength strictly and returns a structured envelope with risks and next recommended steps. It requires clear change proposals to produce accurate domain-grouped spec artifacts.

Related Skills

Explore More Software Engineering Skills→
MarcialFantiniMarcialFantini

sdd-spec

Generate delta specs documenting added, modified, and removed requirements with RFC 2119 keywords.

Community
Advanced
MarcialFantiniMarcialFantini

sdd-init

Detect tech stack and initialize Spec-Driven Development contexts in software projects.

Community
Advanced
dallaydallay

sdd-spec

Generate ADDED, MODIFIED, and REMOVED requirement sections with Given/When/Then scenarios.

Official
Advanced
KilloconQKilloconQ

sdd-spec

Generate delta or full domain specs from change proposals.

Community
Advanced