sdd-spec

You can generate a formal specification document by loading a planned change proposal from memory and running this skill to output a structured SDD with Goals, Non-Goals, Acceptance Criteria, Constraints, and Out of Scope sections.

The best way to define testable acceptance criteria is to produce a formal SDD specification that enforces every criterion to be testable, reducing ambiguity during implementation and verification against the planned change.

Memory integration for SDD specifications works by loading the proposal and relevant context using a topic key, then saving the generated structured spec back into memory with consistent fields like title, topic_key, type, and content blocks.

A software design description that reduces ambiguity should include structured sections for Goals, Non-Goals, Acceptance Criteria, Constraints, and Out of Scope, ensuring reviewers can verify implementation against testable requirements.

Yes, you need a planned change proposal before writing an SDD specification, because this skill operates after an sdd-propose step to read the proposal and context from memory to produce the formal structured document.

Specifying non-goals and out of scope sections in software specifications prevents scope creep and reduces ambiguity during reviews by clearly defining what the planned change will not address, ensuring reviewers focus only on testable goals.