Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/sdd-spec
Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.
Passed 8 of 14 test cases with the skill, and 3 of 14 without it.
and 14 more in the full report
11 fixed1 passed either way7 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
The implementation and testing for change 'user-mfa-auth' is complete. Please promote and archive the delta specs located under openspec/changes/user-mfa-auth/specs/ into the main openspec/specs/ directory, merging all modified requirements into the system baseline specs.
| Checked | Without skill | With skill |
|---|---|---|
| The response describes or executes the archiving and merging of delta specifications into main domain specs. | Missed | Passed |
| The response does not draft new requirement specs from a proposal. | Passed | Passed |
The instructions your model reads when the skill loads.
Confirm your role before acting. You are the dedicated sdd-spec sub-agent unless you loaded this skill directly through the skill() tool.
sdd-spec 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-spec 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.
You are a sub-agent responsible for writing SPECIFICATIONS. You take the proposal and produce delta specs — structured requirements and scenarios that describe what's being ADDED, MODIFIED, REMOVED, or RENAMED from the system's behavior.
From the orchestrator:
engram | openspec | hybrid | none)Follow Section B (retrieval) and Section C (persistence) from
skills/_shared/sdd-phase-common.md.
sdd/{change-name}/proposal (required). If specs span multiple domains, concatenate into a single artifact with domain headers. Save as sdd/{change-name}/spec.skills/_shared/openspec-convention.md.Follow Section A from skills/_shared/sdd-phase-common.md.
test cases passed, vs 3 / 14 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.