sdd-init

Initialize SDD context, testing capabilities, skill registry, and persistence for a project.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-init-zmynxx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/zMynxx/bifrost-with-opencode/tree/main/.opencode/skills/sdd-init
Command: npx skills add https://github.com/zMynxx/bifrost-with-opencode --skill sdd-init-zmynxx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Setting up Spec-Driven Development in a project requires manually detecting the tech stack, test runners, coverage tools, and conventions, then wiring up persistence and registries by hand. This Skill automates that bootstrap so SDD context is detected, recorded, and persisted consistently. ## Core Features & Use Cases - Stack and Tooling Detection: Inspects package.json, go.mod, pyproject.toml, CI, and lint/test configs to identify the real stack, test runner, coverage, linter, type checker, and formatter. - Flexible Persistence Modes: Supports engram, openspec, hybrid, and none modes, writing 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 a pytest-based Python stack, enable strict TDD, persist testing capabilities, and produce a registry for downstream sdd-explore or sdd-new phases. ## Quick Start Ask the agent to run sdd init for this project so it detects the stack, configures strict TDD, and persists the SDD context.

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?▼

Run the sdd-init phase, which inspects files like package.json, go.mod, and pyproject.toml to detect the stack and testing tools. It then persists context, testing capabilities, and a skill registry based on the chosen mode.

What persistence modes does SDD initialization support?▼

Four modes are supported: engram saves context to Engram only, openspec writes openspec/ files only, hybrid does both, and none returns detected context without writing SDD artifacts. The mode is selected via the mode input.

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 initializer reports what already exists and asks before updating it, rather than overwriting existing openspec content. This prevents accidental loss of prior SDD configuration.

What is the skill registry built during SDD init?▼

It is an index written to .atl/skill-registry.md that scans user-level and project-level skill directories, deduplicates by name, and records each skill's name, trigger text, path, and scope. It skips sdd-*, _shared, and skill-registry entries.