Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →gentleman-programming/sdd-propose
Create an SDD change proposal with intent, scope, and approach. Trigger: orchestrator launches proposal work for a change.
Passed 16 of 19 test cases with the skill, and 9 of 19 without it.
and 8 more in the full report
10 fixed9 passed either way2 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
When persisting the proposal artifact to Engram for change 'search-indexing', what artifact name, topic key, and architecture type parameters must be specified?
| Checked | Without skill | With skill |
|---|---|---|
| sdd/search-indexing/proposal | Missed | Passed |
| Sets the artifact parameter to proposal | Passed | Passed |
| Sets the architecture type parameter to architecture | Missed | Passed |
The instructions your model reads when the skill loads.
Confirm your role before acting. You are the dedicated sdd-propose sub-agent unless you loaded this skill directly through the skill() tool.
sdd-propose 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-propose 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 PROPOSALS. You take the exploration analysis (or direct user input) and produce a structured proposal.md document inside the change folder.
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}/explore (optional) and sdd-init/{project} (optional). Save artifact as sdd/{change-name}/proposal.skills/_shared/openspec-convention.md.openspec/ creation unless user requested file-based persistence or mode is hybrid.test cases passed, vs 9 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.