User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…
Install Sdd Verification
$ npx skills add magnus919/hermes-profiles --skill sdd-verification -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install magnus919/hermes-profiles sdd-verification --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/sdd-verification .claude/skills/sdd-verification && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sdd-verification" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-verification into .claude/skills/sdd-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-verification", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-verificationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add magnus919/hermes-profiles --skill sdd-verification -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install magnus919/hermes-profiles sdd-verification --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/sdd-verification .agents/skills/sdd-verification && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sdd-verification" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-verification into .agents/skills/sdd-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-verification", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill sdd-verification -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install magnus919/hermes-profiles sdd-verification --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/sdd-verification .cursor/skills/sdd-verification && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sdd-verification" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-verification into .cursor/skills/sdd-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-verification", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/magnus919/hermes-profiles.git --path skills/sdd-verification--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add magnus919/hermes-profiles --skill sdd-verification -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install magnus919/hermes-profiles sdd-verification --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/sdd-verification .gemini/skills/sdd-verification && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sdd-verification" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-verification into .gemini/skills/sdd-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-verification", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install magnus919/hermes-profiles sdd-verificationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add magnus919/hermes-profiles --skill sdd-verification -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/sdd-verification .github/skills/sdd-verification && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sdd-verification" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-verification into .github/skills/sdd-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-verification", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add magnus919/hermes-profiles --skill sdd-verification -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install magnus919/hermes-profiles sdd-verification --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/magnus919/hermes-profiles.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/sdd-verification .opencode/skills/sdd-verification && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sdd-verification" agent skill from https://github.com/magnus919/hermes-profiles/tree/main/skills/sdd-verification into .opencode/skills/sdd-verification/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sdd-verification", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
sdd-verification- GitHub stars
- 289
- Token cost
- ~1.8k tokens
- SKILL.md length
- 823 words
- Files
- 6 (incl. scripts, references)
- Skills in repo
- 31
- Repo updated
- First seen
- Licence
- MIT
At a glance
SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…
- Implementation needs to be verified against its specification
- SKILL.md covers SDD Pipeline Position, Core Principle: Every AC…, Artifact-Pyramid Output:… and Loading Guidance, plus 4 more sections
- Runs Shell scripts from its folder
- Tasks that involve User stories
What it does
Sdd Verification is an agent skill from magnus919/hermes-profiles. SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant VERIFICATION.md reports. Trigger when implementation needs to be verified against its specification.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including scripts and reference files (for example `references/acceptance-criteria-verification.md`, `references/escalation-protocol.md` and `references/spec-to-test-mapping.md`).
It sits in Product & Project Management, covering User stories. The repository describes itself as: Curated Hermes Agent profiles for specialist swarms — opinionated, Hermes-optimized, artifact-pyramid native. The licence is MIT.
When your agent uses it
- Implementation needs to be verified against its specification
- Tasks that involve User stories
Example prompts
- “/sdd-verification”
Requirements
- A Bash shell
What it can do on your machine
Read from SKILL.md and the folder at commit 867a555. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Sdd Verification loads about 1.8k tokens when it runs, and up to ~3.4k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 823 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from magnus919/hermes-profiles at commit 867a555, republished under its MIT licence (© magnus919). 823 words, ~1,795 tokens.
Download SKILL.mdSave it as
.claude/skills/sdd-verification/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.- name
- sdd-verification
- description
- SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant VERIFICATION.md reports. Trigger when implementation needs to be verified against its specification.
- version
- 1.0.0
- author
- Hermes Agent community
- license
- MIT
SDD Verification
Validating that implementation output satisfies every acceptance criterion defined in the specification. This skill owns the Verify phase of the SDD pipeline — the final gate before delivery.
SDD Pipeline Position
SPECIFY → PLAN → TASKS → IMPLEMENT → [VERIFY]
↑
You are hereVerification is the phase that closes the loop. If specification is the question ("what should the system do?") and implementation is the answer ("this is what the system does"), verification is the judgment ("does the answer satisfy the question?").
Core Principle: Every AC Produces a Binary Verdict
An acceptance criterion that cannot produce a CLEAR PASS or CLEAR FAIL is not a well-defined AC. Verification exposes spec defects: if a criterion is ambiguous and cannot be tested, it is a spec bug, not an implementation failure. Verification findings thus flow in two directions — implementation failures (code doesn't meet the spec) and spec failures (the spec is untestable or ambiguous).
Artifact-Pyramid Output: VERIFICATION.md
Verification reports follow the artifact-pyramid structure:
| Layer | Content | File |
|---|---|---|
| L1 | Pass/fail summary — total ACs tested, pass count, fail count, compliance score, blocking verdict | 00-index.md (entry point) |
| L2 | Verification matrix — per-story or per-feature-area AC status grouped for navigation | Individual *.verification.md files |
| L3 | Individual failure dossiers — what failed, expected behavior (from spec), actual behavior (from implementation), evidence, severity | dossiers/ directory |
| SOURCES | Cross-reference from each AC back to its SPEC.md section | Footer of each file |
Loading Guidance
| Reference | When to load | File |
|---|---|---|
| Acceptance Criteria Verification | Before running verification — methodology for testing ACs that may not have dedicated test infrastructure | references/acceptance-criteria-verification.md |
| Spec-to-Test Mapping | When existing tests exist — how to map test coverage back to spec ACs and identify gaps | references/spec-to-test-mapping.md |
| Escalation Protocol | When an AC is ambiguous or an implementation finding needs escalation — what to do when verification can't produce a clean verdict | references/escalation-protocol.md |
| Template | When to use | File |
|---|---|---|
| VERIFICATION.md | Producing a verification report after implementation | templates/VERIFICATION.md |
| Script | When to run | File |
|---|---|---|
verification-report.sh | After verification — generates the AC pass/fail matrix from structured input | scripts/verification-report.sh |
Trigger Conditions
Invoke this skill when:
- An implementation agent has completed its task and claims acceptance criteria are met
- A PR or MR needs spec-compliance verification before merge
- A spec amendment needs to be verified against existing test coverage
- An integration test suite needs mapping back to the specification's acceptance criteria
Verification Dimensions
Functional Correctness
Does the implementation produce the correct output for each specified input? Test against all normal cases, edge cases, and error conditions from the spec.
Behavioral Completeness
Does the implementation handle every scenario the spec describes? An implementation that handles all normal cases but crashes on a documented edge case is functionally correct for some inputs but behaviorally incomplete.
Contract Compliance
Does the implementation honor the data contracts, interface signatures, and protocol definitions from the spec? A function that returns the right value with the wrong type or shape is not compliant.
Non-Functional Requirements
Does the implementation meet the performance, security, observability, and compliance requirements from the spec? An NFR failure may not produce wrong output but may produce unacceptable behavior in production.
Show full SKILL.md (332 more words)Show less
Negative Testing
Does the implementation correctly reject invalid inputs per the spec? A system that accepts what it should reject is a security and correctness risk, even if it handles valid inputs perfectly.
Severity Classification
| Severity | Definition | Disposition |
|---|---|---|
| BLOCKING | An AC is failed and no workaround exists — the system does not meet a core requirement | Gate does not pass |
| CRITICAL | An AC is failed but a feasible workaround exists | Gate does not pass without documented exception |
| MINOR | An AC passes but with suboptimal behavior, or a non-functional requirement is partially met | Gate can pass with remediation plan |
| INFO | An observation that does not affect pass/fail status — spec improvement suggestion, test gap | Informational |
Gate Verdict Calculation
After classifying each AC by severity, produce a single gate verdict that determines whether the implementation passes to the next SDD phase. The verdict is computed deterministically from severity counts:
| Condition | Verdict |
|---|---|
| 0 BLOCKING, 0 CRITICAL, all ACs tested | APPROVED — the implementation satisfies the specification |
| 0 BLOCKING, ≤2 CRITICAL with remediation plans documented | CONDITIONS — implementation passes but requires tracked remediation of CRITICAL failures |
| Any BLOCKING failure | REJECTED — core requirement unmet; remediation must be completed and re-verified |
| ≥3 CRITICAL failures without documented remediation plans | REJECTED — unacceptable failure density without resolution path |
| < 90% compliance score without documented exception | REJECTED — overall quality below threshold |
The Gate Verdict MUST be included in the L1 summary of every VERIFICATION.md. This makes the verification output directly consumable by the downstream sdd-review phase gate.
Remediation Recommendation Format
Each BLOCKING, CRITICAL, and MINOR finding in the L3 dossiers SHOULD include a remediation recommendation following this structure:
- What to fix: The specific code, config, or behavior that needs to change
- Why this severity: The impact that justifies the severity classification
- Verification for the fix: How to confirm the fix satisfies the AC (specific test or check)
Remediation recommendations are guidance for the implementation agent — they are NOT spec amendments. If the remediation suggests a spec change (ambiguous AC, missing AC), escalate per the Escalation Protocol instead.
© magnus919, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 5 other files (scripts, references) in skills/sdd-verification of magnus919/hermes-profiles.
- SKILL.md
- references/acceptance-criteria-verification.md
- references/escalation-protocol.md
- references/spec-to-test-mapping.md
- scripts/verification-report.sh
- templates/VERIFICATION.md
Open the folder on GitHubat commit 867a555
Compare with similar skills
Sdd Verification next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sdd Verification this skillmagnus919/hermes-profiles | 289 | — | ~1.8k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from magnus919/hermes-profiles
All 31 skills in this repoData Scientist
magnus919/hermes-profiles
PhD-level expertise in data science, statistics, and machine learning.
Brand Designer
magnus919/hermes-profiles
Create comprehensive brand identity documentation for any brand.
Sdd Authoring
magnus919/hermes-profiles
Specification authoring for AI-native SDD — writes formal specifications in structured formats (Gherkin, user stories, acceptance criteria), enforces spec quality gates, and produces…
Sdd Work Decomposition
magnus919/hermes-profiles
SDD work decomposition — translates formal specifications into dependency-aware task plans with per-task acceptance criteria.
Artifact Pyramids
magnus919/hermes-profiles
Progressive disclosure for what AI agents produce. An agent skill from magnus919/hermes-profiles.
SEO Audit
magnus919/hermes-profiles
Full-spectrum SEO + AEO audit skill — technical crawl analysis, on-page content optimization, structured data (JSON-LD/Schema.org) validation, Ghost CMS metadata completion, answer engine…
Related
Categories
Questions about Sdd Verification
What does Sdd Verification do?
SDD acceptance criteria verification — maps specification acceptance criteria to tests, validates implementation output against spec requirements, and produces artifact-pyramid-compliant…. Sdd Verification is an agent skill from magnus919/hermes-profiles.md reports.
When should I use Sdd Verification?
Sdd Verification fits situations like: implementation needs to be verified against its specification; tasks that involve User stories.
How do I install Sdd Verification in Claude Code?
Run `npx skills add magnus919/hermes-profiles --skill sdd-verification -a claude-code`. Or copy the skill folder (skills/sdd-verification in magnus919/hermes-profiles) into .claude/skills/sdd-verification in your project. Claude Code loads it when a task matches its description.
How do I install Sdd Verification in Codex?
Run `npx skills add magnus919/hermes-profiles --skill sdd-verification -a codex`. Or copy the skill folder (skills/sdd-verification in magnus919/hermes-profiles) into .agents/skills/sdd-verification in your project. Codex loads it when a task matches its description.
Can I use Sdd Verification in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add magnus919/hermes-profiles --skill sdd-verification -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sdd-verification, .gemini/skills/sdd-verification, .github/skills/sdd-verification and .opencode/skills/sdd-verification in your project.
What does Sdd Verification need to run?
Going by SKILL.md and its folder, Sdd Verification needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Sdd Verification access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Sdd Verification safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Sdd Verification use?
Sdd Verification is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Sdd Verification use?
About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.
What are the alternatives to Sdd Verification?
Skills that share tags, products or a category with Sdd Verification: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Sdd Verification?
magnus919 (a GitHub user) maintains it in magnus919/hermes-profiles, which has 289 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on June 27, 2026.
Source: magnus919/hermes-profiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.