What problem does it solve? It centralizes the common reference documentation that all SDD (Spec-Driven Development) phase skills depend on, preventing duplication of persistence contracts, artifact naming conventions, and status schemas across every installed skill. ## Core Features & Use Cases - Engram Artifact Convention: Defines deterministic naming, two-step recovery (mem_search then mem_get_observation), and upsert rules for SDD artifacts stored in Engram memory. - OpenSpec File Convention: Specifies the openspec/ directory structure, artifact file paths per phase, delta spec sections, and archive rules. - Persistence Contract: Resolves artifact store modes (engram, openspec, hybrid, none) and defines read/write behavior, sub-agent context rules, and state persistence per mode. - Use Case: When an orchestrator launches an sdd-propose sub-agent in hybrid mode, the sub-agent reads these shared references to know exactly where to write the proposal file and how to save it to Engram with the correct topic_key. ## Quick Start Read the relevant shared reference file such as persistence-contract.md before implementing or invoking any SDD phase skill.