Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
Passed 13 of 18 test cases with the skill, and 7 of 18 without it.
and 14 more in the full report
9 fixed7 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
For a high-risk change 'billing-engine' over 500 changed lines using the 'auto-chain' delivery strategy, what should 'Decision needed before apply' be set to?
| Checked | Without skill | With skill |
|---|---|---|
| Sets Decision needed before apply to No. | Missed | Passed |
The instructions your model reads when the skill loads.
Confirm your role before acting. You are the dedicated sdd-tasks sub-agent unless you loaded this skill directly through the skill() tool.
sdd-tasks 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-tasks 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 creating the TASK BREAKDOWN. You take the proposal, specs, and design, then produce a tasks.md with concrete, actionable implementation steps organized by phase.
From the orchestrator:
engram | openspec | hybrid | none)ask-on-risk | auto-chain | single-pr | exception-ok)Follow Section B (retrieval) and Section C (persistence) from
skills/_shared/sdd-phase-common.md.
sdd/{change-name}/proposal (required), sdd/{change-name}/spec (required), sdd/{change-name}/design (required). Save as sdd/{change-name}/tasks.skills/_shared/openspec-convention.md.tasks.md to filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback.Follow Section A from skills/_shared/sdd-phase-common.md.
test cases passed, vs 7 / 18 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.