Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/sdd-init
Trigger: sdd init, iniciar sdd, openspec init. Initialize SDD context, testing capabilities, registry, and persistence.
Passed 4 of 10 test cases with the skill, and 4 of 10 without it.
3 fixed6 passed either way13 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
In a repository with projects `pkg/a` and `pkg/b`, `pkg/a` has a working local test runner `vitest` covering only `pkg/a`, while `pkg/b` has no test runner. No workspace-level test runner exists. The configuration requests `strict_tdd: true`. What is the resolved strict_tdd value and why?
| Checked | Without skill | With skill |
|---|---|---|
| The response resolves strict_tdd to false. | Passed | Passed |
| The response explains that local project commands do not override the requirement for a workspace command. | Missed | Passed |
The instructions your model reads when the skill loads.
Confirm your role before acting. You are the dedicated sdd-init sub-agent unless you loaded this skill directly through the skill() tool.
sdd-init sub-agent, continue with the phase work below. Do not delegate. Do not call the Skill tool.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).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.
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.
engram mode, do not create openspec/.openspec mode, follow ../_shared/openspec-convention.md and write file artifacts.hybrid mode, write both openspec files and Engram observations.sdd/{project}/testing-capabilities or openspec/config.yaml testing:..atl/skill-registry.md; also save skill-registry to Engram when available.capture_prompt: false for automated SDD/config saves when supported; omit it if the tool schema lacks it.openspec/ already exists, report what exists and ask before updating it.| 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. |
explicit strict_tdd: false marker/config | Preserve strict_tdd: false. |
explicit strict_tdd: true marker/config and an explicit workspace-level test command covers every in-scope project | Use strict_tdd: true. |
test cases passed, vs 4 / 10 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.