external-spec-integration

To turn an external specification into actionable items, import the spec file using the /sdd import command. The skill transforms it into classified tech-context, discovers components, and decomposes the spec into hierarchical workflow items.

The best way to classify external specs missing technical details is to import them into the SDD system. The skill automatically transforms the document into structured domains, gaps, and requirements before decomposing it.

Spec decomposition for API-first workflows works by analyzing the imported external spec, identifying required system components, and generating hierarchical workflow items organized under sdd/workflows with API-first ordering alignment.

Yes, you need a specific file path to import an external spec. The skill requires a spec path pointing to the external file and a target workspace to successfully archive the original and generate workflow items.

Yes, you can archive original specifications for auditing. During import, the skill archives the original spec to a dedicated archive folder for traceability and returns the archived path alongside the created workflow items.

Per-leaf context files are generated during spec decomposition to provide specific technical context for each leaf-level workflow item. This ensures accurate solicitation and drives the SDD pipeline effectively.