SkillAgentSearch skills...

gentle-sdd-verify

Validate implementation matches specs, design, and tasks

Install / Use

npx skills add Soproyectos/grupo-security-office

Installs into whichever agent you are using.

About this skill
⚡

Claude Commands

Claude Code slash commands

Quality Score

39/100

Supported Platforms

Claude Code

Our assessment of gentle-sdd-verify

gentle-sdd-verify scores 39/100 on our quality scale, 4370th of 4,598 Development & Engineering skills we index.

Its Claude Commands is 3.3 KB long, written without headings and no code examples: a solid amount of guidance for an agent.

It has no GitHub stars yet, so there is no community track record; judge it on its content.

Substance
26/30
Structure
0/20
Description
8/15
Adoption
0/20
Freshness
5/15

Maintenance, license and trust

  • We could not determine when the repository was last updated.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-10-15. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

gentle-sdd-verify compared with similar skills

All 4 of these similar skills score higher than gentle-sdd-verify; compare them before choosing.

SkillScoreStarsUpdatedFormat
gentle-sdd-verify (this skill)by Soproyectos390—Claude Commands
claude-memby thedotmack100100.9k1d agoCLAUDE.md
Agent-Reachby Panniantong10097.6ktodayCLAUDE.md
taste-skillby Leonxlnx10097.0k1d agoCLAUDE.md
Understand-Anythingby Egonex-AI10086.4k3d agoCLAUDE.md

Frequently asked questions

How do I install gentle-sdd-verify?
Run npx skills add Soproyectos/grupo-security-office. The install tabs above show the steps for each supported agent.
Which AI agents does gentle-sdd-verify work with?
It is written for Claude Code, as a Claude Commands file. Other agents that read the same format can often use it too.
Is gentle-sdd-verify safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is gentle-sdd-verify still maintained?
We could not determine when the repository was last updated.

description: Validate implementation matches specs, design, and tasks

If the native sdd-verify sub-agent is available, delegate this command to it. Otherwise, read the skill file at ~/.claude/skills/sdd-verify/SKILL.md FIRST, then follow its instructions exactly inline.

CONTEXT:

  • Working directory: Detect agent-side before proceeding by running git rev-parse --show-toplevel with the Bash tool; if that fails, run pwd with the Bash tool.
  • Current project: Derive agent-side from the detected working directory basename. Do not use slash-command shell interpolation for this value.
  • Artifact store mode: engram

TASK: Verify the active SDD change. Read the available proposal, specs, design, and tasks artifacts. Then:

This is optional practical verification, including partial diagnostics, with no review-state prerequisite. Report findings without an automatic review/refuter/fix loop. After verify returns, rerun native SDD status and route only from its refreshed nextRecommended. Completed implementation normally proceeds toward archive regardless of diagnostic findings; unfinished implementation normally returns to apply. Do not offer or invoke RDD; do not call gentle-ai review status.

STATUS GATE: Read ~/.claude/skills/_shared/sdd-status-contract.md and produce structured status before acting. If $ARGUMENTS is missing or ambiguous, ask the user to choose and STOP. Do not guess. Missing inputs limit conclusions, not useful partial diagnostics; report missing artifacts and unavailable checks honestly, and never invent passing checks or completed tasks. If status reports workspace-planning, STOP and explain that full workspace implementation verification is not supported in this slice. Carry contextFiles, task progress, dependency states, and actionContext into the native sub-agent prompt when delegating.

ENGRAM PERSISTENCE (artifact store mode: engram): CRITICAL: mem_search returns 300-char PREVIEWS, not full content. Call mem_get_observation(id) for every found artifact; do not invent IDs for missing artifacts. STEP A — SEARCH (get IDs only): mem_search(query: "sdd/{change-name}/spec", project: "{project}") → save spec_id mem_search(query: "sdd/{change-name}/design", project: "{project}") → save design_id mem_search(query: "sdd/{change-name}/tasks", project: "{project}") → save tasks_id STEP B — RETRIEVE FULL CONTENT FOR FOUND ARTIFACTS: if spec_id exists: mem_get_observation(id: spec_id) → full spec if design_id exists: mem_get_observation(id: design_id) → full design if tasks_id exists: mem_get_observation(id: tasks_id) → full tasks Save report: mem_save(title: "sdd/{change-name}/verify-report", topic_key: "sdd/{change-name}/verify-report", type: "architecture", project: "{project}", capture_prompt: false, content: "{verification report}") Set capture_prompt: false when the Engram tool schema supports it; if an older schema rejects or does not expose the field, omit it rather than failing.

Then:

  1. Report observed completed and unfinished tasks without changing their state.
  2. Check correctness — does code match specs?
  3. Check coherence — were design decisions followed?
  4. Run tests and build (real execution)
  5. Build the spec compliance matrix

Return a structured verification report with: status, executive_summary, detailed_report, artifacts, and next_recommended.

Related Skills

View on GitHub
GitHub Stars0
CategoryDevelopment
UpdatedNaNy ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low