sdd-init

Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.

Quality

66%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./internal/assets/skills/sdd-init/SKILL.md

ORCHESTRATOR GATE: If you loaded this skill via the skill() tool, you are the ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate to the dedicated sdd-init sub-agent using your platform's delegation primitive (e.g., task(...), sub-agent invocation, etc.). This skill is for EXECUTORS only.

Activation Contract

Run this phase when the orchestrator/user asks to initialize SDD in a project. You are the phase executor: do the work yourself, do not delegate, and do not behave like the orchestrator.

Hard Rules

Detect the real stack, conventions, architecture, testing tools, and persistence mode; never guess.
In engram mode, do not create openspec/.
In openspec mode, follow ../_shared/openspec-convention.md and write file artifacts.
In hybrid mode, write both openspec files and Engram observations.
Always persist testing capabilities separately as sdd/{project}/testing-capabilities or openspec/config.yaml testing:.
Always build .atl/skill-registry.md; also save skill-registry to Engram when available.
Use capture_prompt: false for automated SDD/config saves when supported; omit it if the tool schema lacks it.
If openspec/ already exists, report what exists and ask before updating it.

Decision Gates

Input	Action
`mode=engram`	Save context and capabilities to Engram only.
`mode=openspec`	Create/update openspec bootstrap files only.
`mode=hybrid`	Do both Engram and openspec persistence.
`mode=none`	Return detected context only; write no SDD artifacts except registry if required.
strict TDD marker/config found	Use that value.
no marker/config but test runner exists	Default `strict_tdd: true`.
no test runner	Set `strict_tdd: false` and explain unavailable.

Execution Steps

Inspect project files (package.json, go.mod, pyproject.toml, CI, lint/test config) and summarize stack/conventions.
Detect test runner, test layers, coverage, linter, type checker, and formatter.
Resolve Strict TDD from agent marker, openspec/config.yaml, detected runner fallback, or no-runner fallback.
Initialize persistence for the resolved mode.
Build .atl/skill-registry.md using the skill-registry scan rules.
Persist testing capabilities and project context.
Return the structured initialization envelope.

Output Contract

Return status, executive_summary, artifacts, next_recommended, and risks. Include project, stack, persistence mode, Strict TDD status, testing capability table, saved observation IDs/paths, registry path, and next /sdd-explore or /sdd-new step.

References

references/init-details.md — detection checklist, Engram payloads, config skeleton, and output templates.
../_shared/engram-convention.md — Engram artifact naming.
../_shared/openspec-convention.md — openspec layout and rules.

Repository: sergiodvillegas-art/gentle-ai
Commit: 3bfa934

Last updated: 6 days ago
Created: 6 days ago

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.