skills.rest
mrp4sten
mrp4stenCOMMUNITY
Explore all skills by this author →
GitHub

sdd-spec

Generate delta specifications in openspec format with RFC 2119 keywords.

3|Updated Apr 5, 2023
Search Tags:#requirements#scenarios#openspec#change-management#delta-spec#specification-writing#RFC-2119
One-click install
npx skills add https://github.com/mrp4sten/.dotfiles --skill sdd-spec-mrp4sten
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/mrp4sten/.dotfiles/tree/main/development/IA/opencode/skill/sdd-spec
Command: npx skills add https://github.com/mrp4sten/.dotfiles --skill sdd-spec-mrp4sten

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Delta-driven changes often lack structured, testable requirements and scenarios. This skill generates delta specifications that clearly describe what is ADDED, MODIFIED, or REMOVED when a change proposal is processed.

Core Features & Use Cases

  • Identify affected domains from the proposal and group changes by domain.
  • Read existing specs to determine current behavior and produce precise delta updates.
  • Produce spec documents in the openspec format, with clear RFC 2119 keywords and testable scenarios.

Quick Start

Provide delta specs for the latest proposal to begin the delta-spec workflow.

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 for software change proposals?▼

To generate delta specifications, provide a change proposal to parse added, modified, or removed requirements and scenarios. The skill outputs openspec formatted documents with RFC 2119 keywords, organizing changes by domain.

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

A delta spec captures the precise added, modified, or removed requirements and scenarios for a specific software change. You need delta specs when delta-driven changes require structured, testable requirements and clear behavior updates.

How do I write openspec requirements with RFC 2119 keywords and testable scenarios?▼

You can write openspec requirements by processing existing specs and a change proposal. The skill generates full or delta specifications ensuring each requirement has at least one testable scenario and clear RFC 2119 keywords.

Does the delta spec workflow require existing open specs and project config files?▼

Yes, the delta spec workflow reads existing open specs and project config to determine current behavior. This ensures the generated delta updates precisely reflect the added, modified, or removed items from your change proposal.

Can I group software change requirements by domain automatically?▼

Yes, you can group software change requirements by domain automatically. The skill identifies affected domains from your proposal and organizes the parsed added, modified, or removed requirements and scenarios accordingly.

Related Skills

Explore More Software Engineering Skills→
KilloconQKilloconQ

sdd-spec

Generate delta or full domain specs from change proposals.

Community
Advanced
kurojskurojs
2

sdd-spec

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

Community
Intermediate
kryptobaseddevkryptobaseddev
160

ct-spec-writer

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

Community
Intermediate
evandrodevbrevandrodevbr
1

openspec-sync-specs

Merge OpenSpec delta specification changes into main specification documents.

Community
Advanced