sdd-init

Initialize SDD context and bootstrap persistence backend for spec-driven development.

Updated Nov 19, 2024
One-click install
npx skills add https://github.com/Strocs/.dotfiles --skill sdd-init-strocs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/Strocs/.dotfiles/tree/main/.config/opencode/skills/sdd-init
Command: npx skills add https://github.com/Strocs/.dotfiles --skill sdd-init-strocs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates initializing a Spec-Driven Development (SDD) context in a repository by detecting the project's tech stack, conventions, and persisting or bootstrapping the appropriate SDD backend to remove manual setup and reduce onboarding friction.

Core Features & Use Cases

  • Detects project stack and conventions by inspecting common manifests and configuration (for example package.json, go.mod, pyproject.toml, linters, and CI configs).
  • Resolves persistence mode (engram, openspec, none) according to the shared persistence contract and either persists context or bootstraps an openspec workspace.
  • When openspec mode is selected, generates a concise openspec/config.yaml and the openspec/specs and openspec/changes directory layout while avoiding placeholder spec creation.
  • Use case: Onboard a new repository for SDD, prepare a project for spec-driven changes, or recover and report existing openspec content for safe updates.

Quick Start

Initialize the SDD context in this repository and bootstrap openspec persistence when detected.

Frequently Asked Questions about sdd-init

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

FAQPage Schema
How do I bootstrap spec-driven development in an existing repository?

Spec-driven development initialization works by inspecting common manifests and CI configs to detect your stack, resolving a persistence mode like engram or openspec, then generating the required SDD configuration and directory artifacts.

What is openspec persistence mode and when is it needed?

Openspec persistence mode is needed when you want to persist SDD context across sessions; it bootstraps an openspec/config.yaml and generates the openspec/specs and openspec/changes directory layout without creating placeholder specs.

Can I use spec-driven development initialization with my Python or Go project?

Yes, spec-driven development initialization supports Python and Go projects by detecting common manifests like pyproject.toml and go.mod to resolve your stack conventions before applying the appropriate SDD persistence backend.

Does spec-driven development bootstrap work without creating placeholder specs?

Yes, when the openspec persistence mode is selected, the spec-driven development bootstrap generates the openspec/specs and openspec/changes directories while explicitly avoiding the creation of placeholder spec files.

What is the best way to onboard a new repository for spec-driven changes?

The best way to onboard a new repository for spec-driven changes is to automate SDD context initialization, which detects project conventions, resolves persistence mode, and bootstraps the appropriate backend to reduce manual setup friction.

Why does SDD initialization need to detect project manifests and architecture patterns?

Spec-driven development initialization detects project manifests and architecture patterns to accurately resolve the persistence mode and ensure generated configuration and directory artifacts follow your project's specific conventions and safety rules.