yechua-silva/zyrocli/sdd-spec
Claude Code and agent skill by yechua-silva/zyrocli
- community
Checking that the SKILL.md file is still in the repository.
Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.
Install
npx vskill@latest install yechua-silva/zyrocli/sdd-specSKILL.md
The same SKILL.md was published earlier as yechua-silva/zyrocli/sdd-spec.
ORCHESTRATOR GATE: If you loaded this skill via theskill()tool, you arethe ORCHESTRATOR — STOP. Do NOT execute these instructions inline. Delegate tothe dedicatedsdd-specsub-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-spec 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 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.
What You Receive
From the orchestrator:
- Change name
- 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}/proposal(required). If specs span multiple domains, concatenate into a single artifact with domain headers. Save assdd/{change-name}/spec. - openspec: Read and follow
skills/_shared/openspec-convention.md. - hybrid: Follow BOTH conventions — persist to Engram (single concatenated artifact) AND write domain files to filesystem.
- none: Return result only. Never create or modify project files.
What to Do
Step 1: Load Skills
Follow Section A from skills/_shared/sdd-phase-common.md.
Step 2: Identify Affected Domains
Read the proposal's Capabilities section — this is your primary contract:
If the proposal has no Capabilities section (older format), fall back to inferring from "Affected Areas". But always prefer the explicit Capabilities mapping when present.
Step 3: Read Existing Specs
IF mode is `openspec` or `hybrid`: If openspec/specs/{domain}/spec.md exists, read it to understand CURRENT behavior. Your delta specs describe CHANGES to this behavior.
IF mode is `engram`: Existing specs were already retrieved from Engram in the Persistence Contract. Skip filesystem reads.
IF mode is `none`: Skip — no existing specs to read.
Step 4: Write Delta Specs
IF mode is `openspec` or `hybrid`: Create specs inside the change folder:
IF mode is `engram` or `none`: Do NOT create any openspec/ directories or files. Compose the spec content in memory — you will persist it in Step 5.
MODIFIED Requirements Workflow (CRITICAL — read before writing deltas)
When writing a ## MODIFIED Requirements section, follow this exact workflow:
Delta Spec Format
For NEW Specs (No Existing Spec)
If this is a completely new domain, create a FULL spec (not a delta):
Step 5: Persist Artifact
This step is MANDATORY — do NOT skip it.
Follow Section C from skills/_shared/sdd-phase-common.md.
- artifact:
spec - topic_key:
sdd/{change-name}/spec - type:
architecture
Step 6: Return Summary
Return to the orchestrator:
Rules
- ALWAYS use Given/When/Then format for scenarios
- ALWAYS use RFC 2119 keywords (MUST, SHALL, SHOULD, MAY) for requirement strength
- Read the proposal's Capabilities section first — it tells you exactly which spec files to create
- If existing specs exist, write DELTA specs (ADDED/MODIFIED/REMOVED sections)
- If NO existing specs exist for the domain, write a FULL spec
- Every requirement MUST have at least ONE scenario
- Include both happy path AND edge case scenarios
- Keep scenarios TESTABLE — someone should be able to write an automated test from each one
- DO NOT include implementation details in specs — specs describe WHAT, not HOW
- MODIFIED requirements MUST be the FULL block — copy entire requirement + all scenarios from main spec, then edit. Partial MODIFIED blocks lose content at archive time.
- If adding new behavior without changing existing behavior → use ADDED, not MODIFIED
- REMOVED requirements MUST include Reason and SHOULD include Migration when consumers, persisted behavior, docs, or tests are affected
- RENAMED requirements MUST state both old and new names explicitly and SHOULD include Migration guidance for references/tests/docs
- Apply any
rules.specsfromopenspec/config.yaml - Size budget: Spec artifact MUST be under 650 words. Prefer requirement tables over narrative descriptions. Each scenario: 3-5 lines max.
- Return envelope per Section D from
skills/_shared/sdd-phase-common.md.
RFC 2119 Keywords Quick Reference
| Keyword | Meaning | |
|---|---|---|
| MUST / SHALL | Absolute requirement | |
| MUST NOT / SHALL NOT | Absolute prohibition | |
| SHOULD | Recommended, but exceptions may exist with justification | |
| SHOULD NOT | Not recommended, but may be acceptable with justification | |
| MAY | Optional |
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-spec/SKILL.md
Popularity
- 7-day trend score
- 0
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-spec)