skills.rest
Portmeo
PortmeoCOMMUNITY
Explore all skills by this author →
GitHub

sdd-spec

Generate delta specifications with ADDED, MODIFIED, and REMOVED requirements using RFC 2119 keywords.

Updated Aug 23, 2026
Search Tags:#documentation#specification#requirements#change management#delta specs#scenario writing
One-click install
npx skills add https://github.com/Portmeo/rag-chat-project --skill sdd-spec-portmeo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/Portmeo/rag-chat-project/tree/main/.claude/skills/sdd-spec
Command: npx skills add https://github.com/Portmeo/rag-chat-project --skill sdd-spec-portmeo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of documenting changes by generating structured requirements and scenarios, ensuring clarity and consistency in software development specifications.

Core Features & Use Cases

  • Delta Specification Generation: Creates detailed ADDED, MODIFIED, and REMOVED requirements and scenarios for specific changes.
  • Domain-Specific Structuring: Organizes specifications by affected system domains (e.g., auth, payments).
  • Use Case: When a new feature is proposed, this Skill can automatically generate the delta specifications based on the change proposal, outlining exactly how the system's behavior will be altered.

Quick Start

Use the sdd-spec skill to write delta specifications for the change named 'user-profile-update'.

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

You can write delta specifications by generating detailed ADDED, MODIFIED, and REMOVED requirements with testable scenarios for specific software changes. This process ensures structured documentation by organizing specifications according to affected system domains.

What are delta specs and when do I need them for change management?▼

Delta specs are structured requirement documents detailing added, modified, and removed behaviors for a proposed software change. You need them when proposing new features to automatically outline exactly how the system's behavior will be altered.

How do I generate testable scenarios using RFC 2119 keywords for requirements?▼

Testable scenarios using RFC 2119 keywords are generated alongside delta specifications to define precise requirement behaviors. This ensures clarity and consistency by outlining exact system alterations with standardized terminology.

Can I use artifact store modes like engram or openspec for specification persistence?▼

Yes, delta specifications support multiple artifact store modes including engram, openspec, and none. These modes adhere to defined persistence contracts and conventions for maintaining structured documentation.

Does this approach organize specifications by affected system domains?▼

Yes, domain-specific structuring organizes generated specifications by affected system domains such as auth or payments. This ensures changes are clearly categorized and consistently documented across the software.

What is the best way to document added, modified, and removed requirements?▼

The best way to document added, modified, and removed requirements is through delta specification generation. This creates structured specifications with testable scenarios, ensuring clarity and consistency in software development.

Related Skills

Explore More Software Engineering Skills→
KilloconQKilloconQ

sdd-spec

Generate delta or full domain specs from change proposals.

Community
Advanced
fwdarthfwdarth

sdd-verify

Validate code implementations against specifications through static analysis and execution.

Community
Advanced
dallaydallay

sdd-spec

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

Official
Advanced
TzeusyTzeusy

openspec-sync-specs

Merge delta specification changes into main openspec specification files.

Community
Intermediate