sdd-spec

Generates delta feature specifications with standardized formatting and test scenarios.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/carlosamesar/framework-sdd --skill sdd-spec-carlosamesar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-spec
Source: https://github.com/carlosamesar/framework-sdd/tree/main/.opencode/skills/sdd-spec
Command: npx skills add https://github.com/carlosamesar/framework-sdd --skill sdd-spec-carlosamesar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables precise and structured creation of system specifications, allowing teams to document changes and requirements efficiently and with clarity.

Core Features & Use Cases

  • Delta Specification Generation: Produce detailed requirements and scenarios describing changes to system behavior for various domains.
  • Consistent Formatting: Ensure all specs use RFC 2119 keywords, given/when/then format, and include comprehensive test scenarios.
  • Use Case: A product team updates a feature, and this Skill helps generate delta specs highlighting added, modified, and removed requirements, facilitating review and implementation.

Quick Start

Launch the sdd-spec skill and provide the change proposal to generate standardized delta specifications for your system update.

Frequently Asked Questions about sdd-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a delta specification in system design?

A delta specification documents specific changes to system behavior, highlighting added, modified, and removed requirements. It supports version control and cross-domain consistency for software development and product management workflows.

How do I write formal system requirements for testability?

You can write testable system requirements by using RFC 2119 keywords and structuring scenarios in a given/when/then format. This approach ensures comprehensive test scenarios and clear behavioral definitions.

What is the best way to document feature updates for engineering review?

The best way to document feature updates is generating a delta spec that formalizes requirement changes. This facilitates implementation and review by clearly separating added, modified, and removed system behaviors.

Can I generate a system specification from a change proposal?

Yes, you can generate a standardized system specification by providing a change proposal. The system creates detailed, well-structured requirement documents emphasizing delta changes and cross-domain consistency automatically.

Does the specification format support version control for system engineering?

Yes, the specification format supports version control by emphasizing delta changes. It allows system engineering and product management teams to track added, modified, and removed requirements efficiently across versions.

When should I use formal scenario descriptions in system requirements?

You should use formal scenario descriptions when your system requirements need strict testability. Structuring scenarios with given/when/then formats and RFC 2119 keywords ensures comprehensive test coverage for complex software updates.