sdd-design

To create a technical design document, this Skill retrieves proposals and specs from artifact stores, then generates architecture decisions, file-level change plans, testing strategies, and migration guidance. It operates across engram, openspec, hybrid, and none persistence modes.

An implementation-ready technical design includes architecture decisions with rationale, data flow diagrams, concrete file changes, interface contracts, testing strategy, and migration or rollout plans. It also tracks open questions to ensure actionable engineering plans.

Yes, you can use OpenSpec mode to persist design documents by writing openspec files directly to the repository filesystem. The Skill follows persistence conventions for engram, openspec, hybrid, and none modes to store the generated design.

Artifact store integration works by using mem_search and mem_get_observation to retrieve full proposal and spec content when required, then persisting the completed architecture decisions and design documents via mem_save or filesystem writes as specified.

You need an implementation-level design before task breakdown when converting a proposal or spec into an actionable plan, ensuring the design is persisted so subsequent pipeline stages like task creation can reliably find and reference it.

Yes, this approach works without external dependencies, operating independently to retrieve specs and persist designs using built-in memory search, observation retrieval, and filesystem write conventions across its supported persistence modes.