skills.rest
albersg
albersgCOMMUNITY
Explore all skills by this author →
GitHub

_shared

Provides shared SDD reference documents for persistence, status, and skill resolution protocols.

Updated Mar 7, 2026
Search Tags:#orchestration#persistence#conventions#sdd#openspec#sub-agents#engram
One-click install
npx skills add https://github.com/albersg/dotfiles --skill shared-albersg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: _shared
Source: https://github.com/albersg/dotfiles/tree/main/dotfiles-opencode/.opencode/skills/_shared
Command: npx skills add https://github.com/albersg/dotfiles --skill shared-albersg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? SDD phase skills need consistent conventions for artifact persistence, status reporting, and skill resolution, but duplicating these rules in every skill causes drift and inconsistency. ## Core Features & Use Cases - Persistence Contract: Defines engram, openspec, hybrid, and none artifact storage modes with read/write behavior per mode. - Naming Conventions: Standardizes Engram topic keys and OpenSpec file paths for all SDD artifacts like proposals, specs, designs, and tasks. - Status & Skill Protocols: Supplies the SDD status schema, sub-agent return envelope format, and the skill resolver protocol for delegating agents. - Use Case: An orchestrator launching an sdd-propose sub-agent relies on these shared references so the sub-agent saves its proposal with the correct topic_key and returns a structured status envelope. ## Quick Start Read the relevant shared reference file such as persistence-contract.md before implementing or invoking any SDD phase skill.

Frequently Asked Questions about _shared

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the _shared skill in the SDD workflow?▼

The _shared directory is a support package containing reference documents consumed by real SDD phase skills. It is not invokable as a skill itself and only provides conventions for persistence, status, and skill resolution.

How do SDD skills persist artifacts to Engram?▼

SDD skills call mem_save with a deterministic topic_key like sdd/{change-name}/{artifact-type}, type architecture, and capture_prompt set to false. The same topic_key enables upserts so re-saving updates rather than duplicates.

What is the difference between engram, openspec, and hybrid modes?▼

Engram mode stores artifacts only in local memory for cross-session recovery, openspec writes files to the repo for team sharing and git history, and hybrid writes to both. None mode returns results inline without persistence.

Why must sub-agents call mem_get_observation after mem_search?▼

mem_search returns only 300-character previews, not full content. Sub-agents must call mem_get_observation with the observation ID to retrieve complete artifact content, otherwise downstream phases produce wrong output.

Can I invoke the _shared skill directly?▼

No, _shared is marked with disable-model-invocation and user-invocable set to false. It exists only as reference documentation loaded by actual SDD phase skills like sdd-propose or sdd-verify.

Related Skills

Explore More Software Engineering Skills→
etrigan16etrigan16

sdd-init

Initializes SDD project context, testing capabilities, and skill registry with configurable persistence modes.

Community
Advanced
Gentleman-ProgrammingGentleman-Programming
6.1k

sdd-onboard

Guides users through a complete Spec-Driven Development cycle on their real codebase.

Official
Advanced
aroca89aroca89

skill-registry

Scan skill directories and write a resolved registry to .atl/skill-registry.md.

Community
Advanced
electroheadfxelectroheadfx
4

gsd-thread

Create and resume persistent context threads for cross-session project work.

Community
Intermediate