sebasmzg/sebas.dot/sdd-spec
Claude Code and agent skill by sebasmzg/sebas.dot
- community
Checking that the SKILL.md file is still in the repository.
Write specifications with requirements and scenarios (delta specs for changes). Trigger: When the orchestrator launches you to write or update specs for a change.
Install
npx vskill@latest install sebasmzg/sebas.dot/sdd-specSKILL.md
The same SKILL.md was published earlier as sebasmzg/sebas.dot/sdd-spec.
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, or REMOVED from the system's behavior.
What You Receive
From the orchestrator:
- Change name
- Artifact store mode (
engram | openspec | hybrid | none)
Execution and Persistence Contract
Read and follow skills/_shared/persistence-contract.md for mode resolution rules.
- If mode is
engram:
CRITICAL: `mem_search` returns 300-char PREVIEWS, not full content. You MUST call `mem_get_observation(id)` for EVERY artifact. If you skip this, you will work with incomplete data and produce wrong specs.
STEP A — SEARCH (get IDs only — content is truncated):
mem_search(query: "sdd/{change-name}/proposal", project: "{project}")→ save ID
STEP B — RETRIEVE FULL CONTENT (mandatory):
mem_get_observation(id: {proposal_id})→ full proposal content (REQUIRED)
DO NOT use search previews as source material.
If specs span multiple domains, concatenate into a single artifact with domain headers.
Save your artifact: `` mem_save( title: "sdd/{change-name}/spec", topic_key: "sdd/{change-name}/spec", type: "architecture", project: "{project}", content: "{your full spec markdown — all domains concatenated}" ) ` topic_key` enables upserts — saving again updates, not duplicates.
(See skills/_shared/engram-convention.md for full naming conventions.)
- If mode is
openspec: Read and followskills/_shared/openspec-convention.md. - If mode is
hybrid: Follow BOTH conventions — persist to Engram (single concatenated artifact) AND write domain files to filesystem. - If mode is
none: Return result only. Never create or modify project files.
What to Do
Step 1: Load Skill Registry
Do this FIRST, before any other work.
- Try engram first:
mem_search(query: "skill-registry", project: "{project}")→ if found,mem_get_observation(id)for the full registry - If engram not available or not found: read
.atl/skill-registry.mdfrom the project root - If neither exists: proceed without skills (not an error)
From the registry, identify and read any skills whose triggers match your task. Also read any project convention files listed in the registry.
Step 2: Identify Affected Domains
From the proposal's "Affected Areas", determine which spec domains are touched. Group changes by domain (e.g., auth/, payments/, ui/).
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.
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.
If mode is engram:
If mode is openspec or hybrid: the file was already written in Step 4.
If mode is hybrid: also call mem_save as above (write to BOTH backends).
If you skip this step, the next phase (sdd-tasks) will NOT be able to find your specs and the pipeline BREAKS.
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
- 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
- Apply any
rules.specsfromopenspec/config.yaml - Return a structured envelope with:
status,executive_summary,detailed_report(optional),artifacts,next_recommended, andrisks
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/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/sebasmzg/sebas.dot/sdd-spec)