sdd-init

Initialize Spec-Driven Development context and generate project structures.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill sdd-init-jnzader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/JNZader/javi-ai/tree/main/delta/overrides/sdd-init
Command: npx skills add https://github.com/JNZader/javi-ai --skill sdd-init-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initialize Spec-Driven Development context in any project. Detects stack, conventions, and bootstraps the active persistence backend.

Core Features & Use Cases

  • Automatically detects the project's tech stack and conventions.
  • Bootstraps the selected persistence backend (openspec, engram, or hybrid) and creates required structures.
  • Supports multiple modes and project-specific persistence configurations.

Quick Start

Run sdd init in your project to detect the stack and bootstrap the 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 for an existing project?

To initialize spec-driven development context, run the bootstrap command in your project directory to automatically detect the tech stack, select a persistence mode, and generate required configuration files and folder structures.

What is the difference between openspec, engram, and hybrid persistence modes?

Persistence modes determine how spec-driven development context is stored. Openspec and engram are distinct backend conventions, while hybrid combines both, allowing the initialization process to select the appropriate mode based on your project's existing conventions.

Can I automatically generate openspec config and directory structures across multiple tech stacks?

Yes, the initialization process inspects your project to detect the tech stack and applies conventions across multiple scenarios, automatically generating openspec/config.yaml, specs/, and changes/ directories as applicable.

Do I need to manually configure SDD directories or will the bootstrap handle it?

You do not need to manually configure directories. The bootstrap handles mode selection, directory creation, and config generation automatically after inspecting the project to detect the underlying stack and required structures.

When should I not use automated SDD context initialization?

You should avoid automated spec-driven development initialization if your project already has an established SDD setup, as the process is specifically designed to apply context only when a project lacks existing configuration.