Sdd Init logo

Sdd Init

OrganizationPopular
Gentleman-Programming
sdd-init

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

Overview

PublisherGentleman-Programming
Repositorygentle-ai
Skill namesdd-init
Stars
7K
Forks
760
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Gentleman-Programming on GitHub. Read the source before you install it.

Installation

Install the Sdd Init AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Gentleman-Programming/gentle-ai.git /tmp/gentle-ai
mkdir -p .claude/skills
cp -r /tmp/gentle-ai/internal/assets/skills/sdd-init .claude/skills/sdd-init
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Sdd Init in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Sdd Init on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Sdd Init is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Execution Role

Confirm your role before acting. You are the dedicated sdd-init sub-agent unless you loaded this skill directly through the skill() tool.

  • If you are the sdd-init sub-agent, continue with the phase work below. Do not delegate. Do not call the Skill tool.
  • If you loaded this skill through the skill() tool, you are the orchestrator. Stop here and delegate to the dedicated sdd-init sub-agent using your platform's delegation primitive (for example, task(...) or a sub-agent invocation).

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 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

InputAction
mode=engramSave context and capabilities to Engram only.
mode=openspecCreate/update openspec bootstrap files only.
mode=hybridDo both Engram and openspec persistence.
mode=noneReturn detected context only; write no SDD artifacts except registry if required.
explicit strict_tdd: false marker/configPreserve strict_tdd: false.
explicit strict_tdd: true marker/config and an explicit workspace-level test command covers every in-scope projectUse strict_tdd: true.
explicit strict_tdd: true marker/config without that workspace-level commandFail closed to strict_tdd: false and explain that downstream execution requires a workspace-wide command.
no marker/config, non-empty discovered project set, and an explicit workspace-level test command covers every in-scope projectDefault strict_tdd: true.
zero projects are discovered or no explicit workspace-level test command covers every in-scope projectSet strict_tdd: false; preserve and report every project-local command, including missing or independent commands; those local facts do not override a workspace-level command that covers every in-scope project. Explain the no-runner or workspace-wide-command fallback.

Execution Steps

  1. Identify the authoritative workspace root. Before classifying a stack or applying any no-runner fallback, discover every in-scope project root from that root using the bounded rules in references/init-details.md.
  2. Inspect each discovered project for package.json, go.mod, pyproject.toml, Cargo.toml, CI, and lint/test config; preserve its relative path and summarize its stack/conventions.
  3. Detect each project's test runner and command, test layers, coverage, linter, type checker, and formatter. Aggregate those project-to-tool associations in the one workspace-level result; never select one project runner for the workspace.
  4. Resolve Strict TDD from an agent marker or openspec/config.yaml only after every discovered project has been evaluated. Set it to true only for a non-empty discovered project set when one explicit workspace-level test command covers every in-scope project. Preserve and report every project-local command, including missing or independent commands; those local facts do not override a workspace-level command that covers every in-scope project. Use the false fallback only when zero projects are discovered or no explicit workspace-level test command covers every in-scope project.
  5. Initialize persistence for the resolved mode.
  6. Build .atl/skill-registry.md using the skill-registry scan rules.
  7. Persist testing capabilities and project context.
  8. 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Sdd Init AI skill do?

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

Why use Sdd Init on TypingMind?

Because you install it once and use it with any model. Sdd Init is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Sdd Init in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Gentleman-Programming/gentle-ai/tree/main/internal/assets/skills/sdd-init. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Sdd Init?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Sdd Init?

As many as you like. As long as a model supports skills, you can use Sdd Init with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Sdd Init AI skill free?

Yes. It is published on GitHub by Gentleman-Programming under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇