sdd-init

Detect tech stack and initialize Spec-Driven Development contexts in software projects.

Updated Jan 24, 2026
One-click install
npx skills add https://github.com/MarcialFantini/saas-template --skill sdd-init-marcialfantini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/MarcialFantini/saas-template/tree/main/.agent/skills/sdd-init
Command: npx skills add https://github.com/MarcialFantini/saas-template --skill sdd-init-marcialfantini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates initializing a Spec-Driven Development (SDD) context by detecting the project's tech stack, conventions, and active persistence backend so teams avoid inconsistent manual setup and fragmented SDD artifacts.

Core Features & Use Cases

  • Automatic detection: Scans files such as package.json, go.mod, pyproject.toml, CI configs, linters, and test frameworks to determine stack and conventions.
  • Persistence mode resolution: Follows the persistence contract to resolve engram, openspec, or none and acts accordingly.
  • Openspec bootstrapping: When openspec mode is selected, creates a concise openspec/config.yaml, specs/, and changes/ structure and returns a structured envelope describing artifacts and next steps. Use case: initialize SDD in a new or legacy repository to create a reproducible specification workflow or to gather a persistence-aware project context for planning changes.

Quick Start

Run the sdd-init skill from the project root to detect the stack, resolve persistence mode, and either bootstrap openspec or return a structured context summary.

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 in an existing project?

Spec-driven development initialization works by scanning your project root for package files, CI configurations, and linters to automatically detect the tech stack and generate the required openspec directory structure.

What is the best way to bootstrap an openspec workflow in a monorepo?

Bootstrapping an openspec workflow in a monorepo detects mixed package layouts across Node.js, Python, or Go, resolving persistence mode to generate openspec config and directory structures for reproducible specifications.

Does spec-driven development bootstrap work with Python and Go projects?

Spec-driven development bootstrap supports Python and Go projects by detecting pyproject.toml and go.mod files alongside CI configs and test frameworks to determine project conventions during setup.

How does persistence mode resolution work when setting up openspec?

Persistence mode resolution follows the persistence contract to select engram, openspec, or none, determining whether the bootstrap creates the openspec directory structure or returns a structured context summary.

Can I use sdd-init to detect CI configuration and test frameworks automatically?

Yes, the bootstrap process detects CI configuration and test frameworks automatically by scanning repository files during initialization to determine tech stack conventions and return a structured envelope with artifacts.

What do I need to set up spec-driven development in a legacy repository?

Setting up spec-driven development in a legacy repository requires accessible package files or CI configurations for stack detection, allowing bootstrap to resolve persistence mode and generate a structured context summary for planning changes.