sdd-spec

To write delta specifications for software changes, you can use this Skill to automatically generate structured ADDED, MODIFIED, and REMOVED requirements based on your proposal. It organizes specifications by affected domains and produces testable scenarios using Given/When/Then formats.

A delta specification in software development details the added, modified, and removed requirements for a specific change. It structures these adjustments by affected system domains and includes corresponding scenarios to clarify exact behavior and testing criteria.

You generate testable scenarios from a feature proposal by analyzing the proposed changes and mapping them to specific system domains. This Skill formats the resulting scenarios using Given/When/Then syntax and RFC 2119 keywords to ensure strict behavioral clarity.

Yes, you can organize software requirements by affected system domains such as authentication or payments. This Skill analyzes your proposal and automatically structures the generated delta specifications into distinct domain categories within a dedicated change folder.

Yes, this specification tool supports RFC 2119 keywords for requirements. It adheres to these standards when generating delta specifications to ensure requirement clarity, consistency, and proper classification of ADDED, MODIFIED, or REMOVED elements.

The best way to document added and removed requirements is to create structured delta specifications within a change folder. This Skill analyzes your proposal and produces organized requirement lists paired with Given/When/Then scenarios for comprehensive change management.