alan-thegentleman/gentle-ai-enterprise/sdd-spec
Claude Code and agent skill by alan-thegentleman/gentle-ai-enterprise
- 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 alan-thegentleman/gentle-ai-enterprise/sdd-specSKILL.md
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 | none)
Execution and Persistence Contract
Read and follow skills/_shared/persistence-contract.md for mode resolution rules.
- If mode is
engram: Read and followskills/_shared/engram-convention.md. Artifact type:spec. Retrieveproposalas dependency. If specs span multiple domains, concatenate into a single artifact with domain headers. - If mode is
openspec: Read and followskills/_shared/openspec-convention.md. - If mode is
none: Return result only. Never create or modify project files.
What to Do
Step 1: 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 2: Read Existing Specs
If openspec/specs/{domain}/spec.md exists, read it to understand CURRENT behavior. Your delta specs describe CHANGES to this behavior.
Step 3: Write Delta Specs
Create specs inside the change folder:
Delta Spec Format
For NEW Specs (No Existing Spec)
If this is a completely new domain, create a FULL spec (not a delta):
Step 4: 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 reviewPassed
- trufflehogPassed, 100 of 100
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/sdd-spec/SKILL.md
Popularity
- Repository stars
- 1
- 7-day trend score
- 3
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 17 Mar 2026, 8 months ago.
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/alan-thegentleman/gentle-ai-enterprise/sdd-spec)