_shared

Centralizes shared conventions for SDD skills using reference documents.

1|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/RamonsDka/the-architect-overlay --skill shared-ramonsdka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _shared
Source: https://github.com/RamonsDka/the-architect-overlay/tree/main/skills/_shared
Command: npx skills add https://github.com/RamonsDka/the-architect-overlay --skill shared-ramonsdka

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This directory provides centralized, reusable references that underpin all SDD skills, ensuring consistent conventions, prompts, and integration guidelines.

Core Features & Use Cases

  • Central reference set: engram-convention.md, openspec-convention.md, persistence-contract.md, sdd-phase-common.md, and skill-resolver.md.
  • Reusable standards for Engram, OpenSpec, and phase workflows to align new and existing skills.
  • Use Case: When designing a new SDD skill, consult these documents to adopt project-wide conventions.

Quick Start

Review this directory to align any new SDD skill with shared conventions and reference documents.

Frequently Asked Questions about _shared

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

FAQPage Schema
How do I standardize SDD conventions across multiple skills?

Standardize SDD conventions by centralizing reference documents for artifact naming, data persistence, and project context loading. This shared directory provides a single source of truth for how skills interact with Engram, OpenSpec, and phase workflows to ensure consistent structure across implementations.

What reference documents do I need to align a new skill with SDD conventions?

To align a new skill with SDD conventions, consult the shared reference set including engram-convention.md, openspec-convention.md, persistence-contract.md, sdd-phase-common.md, and skill-resolver.md. These documents standardize how skills handle data persistence and project context loading.

When should I consult shared conventions for Engram and OpenSpec integration?

Consult shared conventions for Engram and OpenSpec integration when designing or modifying any SDD skill. These reusable standards ensure consistent prompts, integration guidelines, and phase workflows across both new and existing skill implementations within the project.

Does this shared reference set apply to existing SDD skills or only new ones?

This shared reference set applies to both new and existing SDD skills. It centralizes conventions and guidelines to standardize how any skill interacts with Engram, OpenSpec, and phase workflows, ensuring all implementations maintain consistent structure and expectations.

What's the best way to ensure consistent artifact naming in SDD skill development?

Ensure consistent artifact naming in SDD skill development by referencing the centralized persistence contract and convention documents. This directory acts as a single source of truth for artifact naming, data persistence rules, and project context loading expectations.