What problem does it solve? Turning a rough change proposal into a contract that design, execution, and QA stages can validate against is error-prone when done ad hoc. This Skill formalizes proposal.md into a definitive spec.md with firm scope boundaries, acceptance criteria, and tracked open questions. ## Core Features & Use Cases - Inbound Contract Enforcement: Validates proposal_status, Readiness Check gates, and migrates every Open Questions For Spec row into the spec before formalizing. - Proportional Specification: Produces a minimal spec when all readiness gates are clear and the change touches a single surface, otherwise a full artifact. - State Synchronization: Updates state.yaml with stage status, open risks, checkpoints, and the next safe action toward sddl-design. - Use Case: After the sddl-proposal stage approves a change framing, run this stage to produce a compact spec.md that sddl-design can consume without re-reading broad evidence. ## Quick Start Run the sddl-spec stage to formalize the current change's proposal.md into spec.md with scope boundaries and acceptance criteria.