sdd-init

Detect tech stack and initialize Spec-Driven Development context for a project.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/adacosdev/dotfiles --skill sdd-init-adacosdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/adacosdev/dotfiles/tree/main/dot_config/opencode/skills/sdd-init
Command: npx skills add https://github.com/adacosdev/dotfiles --skill sdd-init-adacosdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize Spec-Driven Development context in a project. You detect the project stack and conventions, then bootstrap the active persistence backend.

Core Features & Use Cases

  • Detect project context: tech stack, linting conventions, CI patterns.
  • Bootstrap persistence backend in openspec, engram, or hybrid modes and create necessary structure.
  • Generate a concise project registry and ready-to-use config for SDD workflows.

Quick Start

Run the sdd-init skill in a project to detect context and bootstrap the chosen persistence backend.

Frequently Asked Questions about sdd-init

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

FAQPage Schema
How do I initialize spec-driven development context in a new or existing repository?

Spec-driven development context requires a persistence backend to store artifacts. This initialization bootstraps openspec, engram, or hybrid modes by creating the necessary directory structure based on detected project conventions.

How does project context detection work for SDD initialization?

Project context detection scans package files and configs to identify the tech stack, linting conventions, and CI patterns, then generates a concise project registry and ready-to-use config for SDD workflows.

Can I use openspec and engram persistence modes together in the same project?

Yes, the initialization supports hybrid persistence modes, allowing both openspec and engram to operate together by creating the necessary directory structure to store persistent context and artifacts for both.

Do I need existing configuration files to bootstrap an SDD workflow?

You need project metadata such as package files or configs available so the initialization can auto-detect your tech stack. It applies to both new and existing repositories to generate the ready-to-use SDD config.

What is the best way to set up persistent context for spec-driven development?

The best way to set up persistent context is to run an initialization that auto-detects your stack and bootstraps the backend, generating a project registry and config that adhere to openspec or engram conventions.