What problem does it solve? Translating a change proposal into precise, testable specifications is error-prone: requirements get lost, modified requirements lose scenarios at archive time, and specs drift into implementation detail. This Skill standardizes the spec-writing phase of a spec-driven development (SDD) workflow by producing structured delta specs. ## Core Features & Use Cases - Delta Spec Generation: Produces ADDED, MODIFIED, REMOVED, and RENAMED requirement sections per affected domain, or full specs for new domains. - Strict Format Enforcement: Every requirement uses RFC 2119 keywords (MUST, SHALL, SHOULD, MAY) and at least one Given/When/Then scenario covering happy paths and edge cases. - Multi-Mode Persistence: Supports engram, openspec, hybrid, and none artifact store modes, reading the proposal's Capabilities section to map domains to spec files. - Use Case: An orchestrator launches spec work for a change named "add-oauth-login"; the sub-agent reads the proposal, writes delta specs for the auth domain under openspec/changes/add-oauth-login/specs/, and returns a coverage summary ready for the design phase. ## Quick Start Delegate to the sdd-spec sub-agent with the change name and artifact store mode to generate delta specifications from the existing proposal.