Sdd Verify logo

Sdd Verify

OrganizationPopular
Gentleman-Programming
sdd-verify

Trigger: explicitly requested SDD verification. Run optional practical diagnostics against available implementation and artifacts.

Overview

PublisherGentleman-Programming
Repositorygentle-ai
Skill namesdd-verify
Stars
7K
Forks
760
Bundled files
2
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.

  • 2 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 Verify 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-verify .claude/skills/sdd-verify
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Sdd Verify 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 Verify 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 Verify 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

If you are the dedicated sdd-verify executor, perform the diagnostics below; do not delegate. If you are the orchestrator loading this skill, delegate to that executor.

Activation Contract

Run when the orchestrator explicitly requests verification. Verification is optional, not a prerequisite for archive.

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.

Hard Rules

  • Use the supplied structured status, artifact store, change identity, and edit permissions. Verification grants no mutation authority; do not fix code or tasks.
  • Inspect available artifacts and implementation, including partial work. Missing artifacts limit conclusions, not permission to report useful diagnostics.
  • Preserve user-owned strict_tdd, test commands, and model/provider/profile/effort selection. When Strict TDD is active, load strict-tdd-verify.md and assess the available apply-progress evidence honestly; never fabricate historical RED or GREEN.
  • Report actual command results and limitations. Source inspection, unchecked tasks, and unexecuted tests are not runtime proof. Missing tooling means unavailable checks, not PASS.
  • Do not require a report schema, validator, immutable attestation, evidence search, or settlement. Missing, stale, malformed, or failed reports do not gate archive.
  • SDD never offers, launches, or consumes RDD. Findings do not start automatic review, refuter, or correction loops.
  • Apply rules.verify from openspec/config.yaml to requested diagnostics without treating report format as archive authority.

Decision Gates

ConditionAction
Partial implementation or missing specs/designInspect what exists; name unfinished work and skipped dimensions.
Strict TDD activeCheck actual TDD evidence for implemented work; disclose missing evidence.
Test/build fails or a requirement is unmetReport the finding and its evidence, without editing or certifying completion.
Tooling or permission unavailableReport the limitation; do not bypass authorization.
Workspace-planning contextLimit diagnostics to accessible planning artifacts; do not edit linked repositories.

Execution Steps

  1. Load relevant skills and retrieve available artifacts through shared Sections A/B, using the supplied locators and active store.
  2. Compare implemented behavior with available requirements and design. Record task completion as observed; do not rewrite checkboxes.
  3. Run applicable tests, build/type-check, and other practical project checks within the authorized scope. Adapt depth to the change; do not force exhaustive scenario searches or a fixed evidence matrix.
  4. Record commands, exit codes, useful output, findings, and unavailable or unrun checks. Distinguish verified behavior from assumptions and static observations.
  5. Persist the diagnostic report through shared Section C when the selected store permits it; preserve prior historical findings and identify what changed. Do not rewrite old user reports merely to satisfy a format. Return shared Section D.

Output Contract

Return concise findings, observed task state, executed checks and their outcomes, limitations, and recommended next work. A diagnostic report may be partial or failed; neither blocks archive. Completed implementation normally proceeds to archive; unfinished implementation normally returns to apply. Archive records the actual state, never a synthetic PASS.

References

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 Verify AI skill do?

Trigger: explicitly requested SDD verification. Run optional practical diagnostics against available implementation and artifacts.

Why use Sdd Verify on TypingMind?

Because you install it once and use it with any model. Sdd Verify 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 Verify 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-verify. 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 Verify?

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

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

Is the Sdd Verify 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 👇