Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/sdd-apply
Implement SDD tasks from specs and design. Trigger: orchestrator launches apply for one or more change tasks.
Passed 12 of 17 test cases with the skill, and 6 of 17 without it.
and 7 more in the full report
7 fixed8 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
You are executing batch 2 of the `billing-v2` multi-part change. The workload decision specifies `auto-chain` with strategy `stacked-to-main`. Should PR #2 target the main development branch directly or target PR #1's branch?
| Checked | Without skill | With skill |
|---|---|---|
| Targets the branch created for PR #1 rather than main directly. | Missed | Passed |
The instructions your model reads when the skill loads.
Confirm your role before acting. You are the dedicated sdd-apply sub-agent unless you loaded this skill directly through the skill() tool.
sdd-apply 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-apply 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 IMPLEMENTATION. You receive specific tasks from tasks.md and implement them by writing actual code. You follow the specs and design strictly.
From the orchestrator:
engram | openspec | hybrid | none) — consume it, never re-derive itskills/_shared/sdd-status-contract.md: schemaName, planningHome, changeRoot, artifactPaths, contextFiles, applyState, task progress, dependency states, and actionContextask-on-risk | auto-chain | single-pr | exception-ok, plus PR slice or size:exception when applicable)Follow Section B (retrieval) and Section C (persistence) from
skills/_shared/sdd-phase-common.md.
Reads are store-blind. Read proposal, spec, design, and tasks (all required) from the locators in artifactPaths, and apply-progress from its locator whenever that one resolves. Do not detect the store and do not assemble locators yourself.
Writes name a mechanism because writing a file and saving an observation are different operations, but the reported store selects it — you do not:
mem_update the tasks observation so completed tasks are marked [x]; mem_save or mem_update the apply-progress locator.skills/_shared/openspec-convention.md; mark [x] in the file at the tasks locator.test cases passed, vs 6 / 17 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.