sdd-spec

Generate delta specifications with requirements and scenarios for software changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/felipe3dfx/dotfiles --skill sdd-spec-felipe3dfx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/felipe3dfx/dotfiles/tree/main/skills/sdd-spec
Command: npx skills add https://github.com/felipe3dfx/dotfiles --skill sdd-spec-felipe3dfx

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 specifications, ensuring clarity and consistency in software development.

Core Features & Use Cases

  • Delta Specification Generation: Creates ADDED, MODIFIED, and REMOVED requirements and scenarios for specific domains.
  • Full Specification Generation: Writes complete specifications for new domains.
  • Use Case: When a new feature is proposed, this Skill can automatically generate the detailed requirements and test scenarios needed for development and review.

Quick Start

Use the sdd-spec skill to write delta specifications for the 'user-authentication' change.

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?

Delta specifications document ADDED, MODIFIED, and REMOVED requirements and scenarios for specific domains. You generate them based on existing documentation and proposals to ensure clear, testable software change tracking.

What is the Given/When/Then format for scenario writing?

Given/When/Then is a scenario writing format used for testable specification documentation. It structures scenarios by defining a starting context, an action, and an expected result, adhering to RFC 2119 keywords for clarity.

Can I generate full specifications for a new software domain?

Yes, you can generate full specifications for new domains. This process creates complete sets of requirements and detailed test scenarios needed for development and review when a new feature is proposed.

How do I document modified and removed requirements?

Documenting modified and removed requirements involves generating delta specifications. This identifies specific changes across domains, differentiating between what has been updated and what has been eliminated from the existing software documentation.

Does specification generation support RFC 2119 keywords?

Yes, specification generation adheres to RFC 2119 keywords. This ensures clear, testable documentation by standardizing requirement levels, such as MUST and SHOULD, within the generated software change scenarios.

What is the best way to generate test scenarios for new features?

The best way to generate test scenarios for new features is using Given/When/Then formats within delta specifications. This creates structured, testable requirements directly from existing documentation and feature proposals.