sdd-init

Initialize SDD project context, testing capabilities, skill registry, and persistence configuration.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-init-balthael
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdd-init
Source: https://github.com/Balthael/ciberbal-ai/tree/main/internal/assets/skills/sdd-init
Command: npx skills add https://github.com/Balthael/ciberbal-ai --skill sdd-init-balthael

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Starting spec-driven development in a project requires manually detecting the tech stack, test tooling, and conventions, then wiring up persistence and registries by hand. This Skill automates that bootstrap so SDD phases begin from accurate, detected project context instead of guesses. ## Core Features & Use Cases - Stack and Tooling Detection: Inspects package.json, go.mod, pyproject.toml, CI, and lint/test configs to summarize the real stack, test runner, coverage, linter, type checker, and formatter. - Persistence Modes: Supports engram, openspec, hybrid, and none modes, writing Engram observations, openspec/config.yaml, or both as appropriate. - Skill Registry Generation: Scans user-level and project-level skill directories across many agent platforms and builds .atl/skill-registry.md as an index of available skills. - Use Case: A developer starting spec-driven development on an existing Go or Python repo invokes the init phase to detect testing capabilities, resolve Strict TDD mode, and persist project context before running exploration or proposal phases. ## Quick Start Ask the agent to initialize SDD in this project and detect the stack, testing capabilities, and persistence mode.

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?

Run the sdd-init phase, which inspects files like package.json, go.mod, and pyproject.toml to detect the stack and conventions. It then persists project context, testing capabilities, and a skill registry according to the chosen persistence mode.

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

Engram mode saves context and capabilities only to Engram memory, openspec mode writes openspec/ files including config.yaml, and hybrid mode does both. The none mode returns detected context without writing SDD artifacts.

How is Strict TDD mode determined during initialization?

Strict TDD is resolved from an explicit agent marker or openspec/config.yaml first. If none exists but a test runner is detected, it defaults to true; with no test runner it is set to false with an explanation.

What testing capabilities does the init phase detect?

It detects the test runner and command, unit, integration, and E2E test layers, coverage tooling, and quality tools such as linters, type checkers, and formatters. Results are saved as a structured testing capabilities document.

What happens if openspec/ already exists in the project?

The skill reports what already exists and asks before updating it, rather than overwriting existing openspec artifacts. This prevents accidental loss of prior SDD configuration.