skills.rest
etrigan16
etrigan16COMMUNITY
Explore all skills by this author →
GitHub

_shared

Stores shared SDD reference documents for persistence conventions and phase protocols.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? SDD phase skills need consistent rules for artifact persistence, naming conventions, and sub-agent coordination, but duplicating these rules in every skill creates drift and maintenance burden. ## Core Features & Use Cases - Persistence Contract: Defines the four artifact store modes (engram, openspec, hybrid, none) and their read/write behavior per mode. - Naming Conventions: Provides deterministic Engram topic_key patterns and OpenSpec directory structures for all SDD artifacts. - Common Phase Protocol: Supplies shared boilerplate for skill loading, artifact retrieval, return envelopes, and review workload guards. - Use Case: When an orchestrator launches an sdd-propose sub-agent, the sub-agent reads these shared references to know exactly how to persist its proposal and structure its return envelope. ## Quick Start Read the shared reference files in this directory before executing any SDD phase skill to apply the correct persistence and status contracts.

Frequently Asked Questions about _shared

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

FAQPage Schema
What are the SDD artifact store modes?▼

SDD supports four artifact store modes: engram for cross-session memory, openspec for git-versioned files, hybrid for both simultaneously, and none for ephemeral inline results. The orchestrator asks the user which mode to use at session start.

How do SDD sub-agents persist artifacts to Engram?▼

Sub-agents call mem_save with a deterministic topic_key following the pattern sdd/{change-name}/{artifact-type}, type architecture, and capture_prompt set to false. The topic_key enables upserts so re-running a phase updates rather than duplicates the artifact.

Can the _shared skill be invoked directly?▼

No, _shared is a support package only and is explicitly marked as not invokable with disable-model-invocation set to true. It stores reference documents consumed by real SDD phase skills.

What is the difference between engram and openspec persistence modes?▼

Engram mode provides cross-session recovery and compaction survival but overwrites on upsert with no history. Openspec mode creates git-versioned files with full audit trails and team shareability but no automatic cross-session recovery.

Why must sub-agents end with text instead of a tool call?▼

The Task tool returns only the sub-agent's final output to the parent agent. If the last action is a tool call like mem_save, the parent receives only the tool result and the sub-agent's text analysis is lost.

Related Skills

Explore More Software Engineering Skills→
RamonsDkaRamonsDka
1

_shared

Centralizes shared conventions for SDD skills using reference documents.

Community
Basic
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