sdd-init

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

Updated May 24, 2026
One-click install
npx skills add https://github.com/etrigan16/v0-cipher-ar --skill sdd-init-etrigan16
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/etrigan16/v0-cipher-ar/tree/main/.opencode/skills/sdd-init
Command: npx skills add https://github.com/etrigan16/v0-cipher-ar --skill sdd-init-etrigan16

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up spec-driven development (SDD) in a project requires manually detecting the tech stack, test tooling, and conventions, then wiring up persistence and registries. This Skill automates that initialization so AI agents start with accurate project context. ## Core Features & Use Cases - Stack and Tooling Detection: Inspects package.json, pyproject.toml, go.mod, CI configs, and lint/test setups to identify the real stack, test runner, coverage, linter, and formatter without guessing. - Flexible Persistence Modes: Supports engram, openspec, hybrid, and none modes, writing context to Engram observations, openspec/config.yaml, or both. - Skill Registry Generation: Scans user-level and project-level skill directories to build .atl/skill-registry.md as an index of available skills. - Use Case: When starting SDD on a new repository, run the init phase to detect that the project uses Vitest and pytest, enable strict TDD mode, persist testing capabilities, and produce a registry for downstream phases like /sdd-explore or /sdd-new. ## Quick Start Ask the agent to initialize SDD in this project and detect the stack, testing tools, and persistence mode.

Frequently Asked Questions about sdd-init

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

FAQPage Schema
How do I initialize SDD in an existing project?▼

Invoke the sdd-init phase, which inspects files like package.json, pyproject.toml, and CI configs to detect the stack and test tooling. It then persists context, testing capabilities, and a skill registry according to the chosen mode.

What persistence modes does SDD initialization support?▼

Four modes are supported: engram saves context to Engram observations only, openspec writes openspec/ files only, hybrid does both, and none returns detected context without writing SDD artifacts.

How is strict TDD mode determined during initialization?▼

Strict TDD is resolved from an explicit agent marker or openspec/config.yaml first. If none exists but a test runner is detected, it defaults to true; with no test runner, it is set to false with an explanation.

What happens if openspec/ already exists in the project?▼

The skill reports what already exists and asks before updating it, rather than overwriting existing openspec files. This prevents accidental loss of prior SDD configuration.

Which directories are scanned to build the skill registry?▼

The scan covers user-level skill paths such as ~/.claude/skills and ~/.config/opencode/skills, plus project-level paths like .opencode/skills and .claude/skills. Skills named sdd-*, _shared, and skill-registry are skipped, with project skills preferred on duplicates.