yechua-silva/zyrocli/sdd-propose
Claude Code and agent skill by yechua-silva/zyrocli
- community
Checking that the SKILL.md file is still in the repository.
Create an SDD change proposal with intent, scope, and approach. Trigger: orchestrator launches proposal work for a change.
Install
npx vskill@latest install yechua-silva/zyrocli/sdd-proposeSKILL.md
ORCHESTRATOR GATE: If you loaded this skill via theskill()tool, you arethe ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate tothe dedicatedsdd-proposesub-agent using your platform's delegation primitive(e.g.,task(...), sub-agent invocation, etc.). This skill is for EXECUTORSonly.
Executor Override
If you ARE the sdd-propose 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.
Language Domain Contract
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 Spanish technical artifacts are explicitly requested, use neutral/professional Spanish unless the user explicitly asks for a regional variant.
Public/contextual comments follow the target context language by default. Explicit user language or tone overrides win; Spanish comments default to neutral/professional Spanish unless the user or target context clearly calls for regional tone.
Purpose
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.
What You Receive
From the orchestrator:
- Change name (e.g., "add-dark-mode")
- Exploration analysis (from sdd-explore) OR direct user description
- Artifact store mode (
engram | openspec | hybrid | none)
Execution and Persistence Contract
Follow Section B (retrieval) and Section C (persistence) fromskills/_shared/sdd-phase-common.md.
- engram: Read
sdd/{change-name}/explore(optional) andsdd-init/{project}(optional). Save artifact assdd/{change-name}/proposal. - openspec: Read and follow
skills/_shared/openspec-convention.md. - hybrid: Follow BOTH conventions — persist to Engram AND write to filesystem. Retrieve dependencies from Engram (primary) with filesystem fallback.
- none: Return result only. Never create or modify project files.
- Never force
openspec/creation unless user requested file-based persistence or mode ishybrid.
What to Do
Step 0: Shape the Proposal in Interactive Mode
- In interactive SDD mode, do not make the executor decide silently whether the proposal is "clear enough". Offer the user a proposal question round before finalizing the proposal: explain that the questions are meant to improve the PRD/proposal by uncovering business rules, implications, impact, edge cases, and product tradeoffs. Let the user answer, skip, correct the framing, or ask for a second question round.
- Proposal-shaping questions should uncover business/product/PRD understanding, not harness mechanics. Cover the smallest useful subset of:
- business problem: what pain, opportunity, user confusion, or operational cost makes this change worth doing now;
- target users and situations: who is affected, in which workflow, at what moment, and with what level of urgency;
- business rules: policies, permissions, thresholds, lifecycle rules, compliance/security expectations, or domain invariants the proposal must respect;
- product outcome: what should feel, work, or become possible after the change;
- current-state gap: what is wrong, inconsistent, missing, ad hoc, or hard to explain today;
- implications and impact: which teams, workflows, data, UX expectations, support burden, or operational processes may be affected;
- edge cases: empty states, partial data, failures, permissions, slow paths, unusual customers, migration states, or conflicting user needs;
- decision gaps: which product unknowns would make the proposal ambiguous, risky, or easy to overbuild;
- scope boundaries and non-goals: what belongs in the first product slice, what is later refinement, and what must stay unchanged even if related;
- business risk or tradeoff: what downside matters most if the proposal chooses the wrong direction.
- Prefer 3–5 concrete product questions per round. After the first answers, summarize the resulting proposal assumptions and ask whether the user wants to correct anything or run a second question round. Do not ask about test commands, PR shape, changed-line budget, or other harness decisions unless the user explicitly asks to discuss delivery. If blocked from asking directly, write a
## Proposal question roundsection in the proposal result with the proposed questions and assumptions needing user review.
Step 1: Load Skills
Follow Section A from skills/_shared/sdd-phase-common.md.
Step 2: Create Change Directory
IF mode is `openspec` or `hybrid`: create the change folder structure:
IF mode is `engram` or `none`: Do NOT create any openspec/ directories. Skip this step.
Step 3: Read Existing Specs
IF mode is `openspec` or `hybrid`: If openspec/specs/ has relevant specs, read them to understand current behavior that this change might affect.
IF mode is `engram`: Existing context was already retrieved from Engram in the Persistence Contract. Skip filesystem reads.
IF mode is `none`: Skip — no existing specs to read.
Step 4: Write proposal.md
Step 5: Persist Artifact
This step is MANDATORY — do NOT skip it.
Follow Section C from skills/_shared/sdd-phase-common.md.
- artifact:
proposal - topic_key:
sdd/{change-name}/proposal - type:
architecture
Step 6: Return Summary
Return to the orchestrator:
Rules
- In
openspecmode, ALWAYS create theproposal.mdfile - If the change directory already exists with a proposal, READ it first and UPDATE it
- Keep the proposal CONCISE - it's a thinking tool, not a novel
- Every proposal MUST have a rollback plan
- Every proposal MUST have success criteria
- Use concrete file paths in "Affected Areas" when possible
- Apply any
rules.proposalfromopenspec/config.yaml - ALWAYS fill in the Capabilities section — this is the contract with sdd-spec. Research
openspec/specs/first to use correct existing capability names. - New Capabilities → each will become
openspec/specs/<name>/spec.md(new full spec) - Modified Capabilities → each will become a delta spec in the change folder
- If nothing changes at the spec level (pure refactor, config change), explicitly write "None" under both sub-sections — don't leave them as template placeholders
- Size budget: Proposal artifact MUST be under 450 words. Use bullet points and tables over prose. Headers organize, not explain.
- Return envelope per Section D from
skills/_shared/sdd-phase-common.md.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryChecking.config/opencode/plugins/skills/sdd-propose/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 0
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/yechua-silva/zyrocli/sdd-propose)