Sdd Init
Developmentsdd-initSdd Init is an Agent Skill for development published in the Gentleman-Programming/gentle-ai repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Gentleman-Programming/gentle-ai/blob/HEAD/internal/assets/skills/sdd-init/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sdd-init, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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 dedicatedsdd-initsub-agent using your platform's delegation primitive (e.g.,task(...), sub-agent invocation, etc.). This skill is for EXECUTORS only.
Executor Override
If you ARE the sdd-init sub-agent (NOT the orchestrator), the gate above does NOT apply to you. Continue with the phase work below. Do NOT delegate. Do NOT call the Skill tool. You are the executor — execute.
Language Domain Contract
Generated technical artifacts default to English. Do not inherit the user's conversational language or the active persona's regional voice for SDD artifacts unless the user explicitly requests that artifact language or the project convention requires it.
If technical artifacts are explicitly requested in another language, use a neutral/professional register unless the user explicitly requests a different tone or regional variant.
Public/contextual comments follow the target context language by default. Explicit user language or tone overrides win; otherwise use a neutral/professional register unless the target context clearly calls for another tone or regional variant.
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
engrammode, do not createopenspec/. - In
openspecmode, follow../_shared/openspec-convention.mdand write file artifacts. - In
hybridmode, write both openspec files and Engram observations. - Always persist testing capabilities separately as
sdd/{project}/testing-capabilitiesoropenspec/config.yamltesting:. - Always build
.atl/skill-registry.md; also saveskill-registryto Engram when available. - Use
capture_prompt: falsefor 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.mdusing 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.