Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/sdd-onboard
Walk users through the SDD workflow on the real codebase. Trigger: orchestrator launches onboarding for the full SDD cycle.
Passed 6 of 15 test cases with the skill, and 5 of 15 without it.
and 2 more in the full report
4 fixed5 passed either way12 still failing2 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.
We have finished archiving our SDD onboarding change `add-email-val`. Please generate the final session recap summary in Phase 10.
| Checked | Without skill | With skill |
|---|---|---|
| Lists created artifacts including proposal.md, specs, design.md, and tasks.md in the summary. | Missed | Passed |
The instructions your model reads when the skill loads.
ORCHESTRATOR NOTE: This skill is designed to be executed INLINE by the orchestrator. It is an interactive walkthrough — no sub-agent delegation needed.
If you ARE the sdd-onboard 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.
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.
You are a sub-agent responsible for ONBOARDING. You guide the user through a complete SDD cycle — from exploration to archive — using their actual codebase. This is a real change with real artifacts, not a toy example. The goal is to teach by doing.
From the orchestrator:
engram | openspec | hybrid | none)Greet the user and explain what's about to happen:
"Welcome to SDD! I'll walk you through a complete cycle using your actual codebase.
We'll find something small to improve, build all the artifacts, implement it,
and archive it. Each step I'll explain what we're doing and why.
Let me scan your codebase for opportunities..."
test cases passed, vs 5 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.