sdd-init

Initialize Spec-Driven Development context and detect stack conventions.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/aroca89/roca_teams --skill sdd-init-aroca89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/aroca89/roca_teams/tree/main/skills/sdd-init
Command: npx skills add https://github.com/aroca89/roca_teams --skill sdd-init-aroca89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Initializes Spec-Driven Development context so AI orchestrators stop guessing stacks, conventions, and persistence choices when facing medium to large changes, preventing context decay and misalignment across phases.

Core Features & Use Cases

  • Full stack detection: Inspects package manifests, tooling, and architectural patterns to describe the project landscape accurately.
  • Flexible persistence: Boots up openspec directories, records context to engram, or stays ephemeral based on the requested mode while honoring engram and openspec conventions.
  • Skill registry convergence: Scans personal and project skill folders plus convention files, writes .atl/skill-registry.md, and optionally saves the registry in engram for downstream phases.
  • Use case: Hand the orchestration to sdd-init, specify openspec, and it will prepare config, folders, registry, and context summaries so the rest of the team can immediately run exploration and proposal skills.

Quick Start

Tell the sdd-init skill to bootstrap Spec-Driven Development for this repository using the persistence mode you need.

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 AI-assisted project?

Spec-driven development context initialization prevents AI orchestrators from guessing your tech stack and conventions during large changes, ensuring structured proposals and verifiable persistence artifacts remain aligned across all project workflow phases.

How do I bootstrap openspec directories and engram persistence for a new project?

The initialization process supports flexible persistence, allowing you to choose between booting up openspec directories, recording context to engram, or staying ephemeral based on your requested mode while honoring their respective technical conventions.

Does spec-driven development initialization work without any pre-existing dependencies?

Spec-driven development initialization works without pre-existing dependencies by actively scanning your project landscape, detecting full stack patterns from package manifests, and generating the required convention files automatically during the bootstrap process.

What is the best way to prevent fragmented AI-assisted change flows in software engineering?

Preventing fragmented AI-assisted change flows requires launching spec-driven development context initialization, which establishes stack conventions detection and verifiable persistence artifacts before you orchestrate complex project modifications.

Why does my AI orchestrator lose context alignment across different workflow phases?

AI orchestrators lose context alignment across phases when they lack structured spec-driven development initialization, which causes context decay during medium to large changes by omitting verifiable persistence artifacts and a centralized skill registry.

When should I not use ephemeral mode for spec-driven development context?

Avoid using ephemeral mode for spec-driven development context when downstream phases need to run exploration and proposal skills, because ephemeral mode skips saving the skill registry in engram for later project retrieval.