sdd-spec

Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./internal/assets/skills/sdd-spec/SKILL.md

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete templates and a clearly sequenced workflow backed by critical pitfall warnings. Its main weaknesses are mild verbosity (redundant gate/override framing, a long language-register contract) and an inline-heavy structure that could split detail into reference files.

Suggestions

Collapse the "ORCHESTRATOR GATE" and "Executor Override" sections into a single concise delegation rule to remove redundancy.

Trim the "Language Domain Contract" to the essential rule plus the override condition, dropping the repeated neutral-register elaboration.

Move the full delta-spec template and RFC 2119 quick reference into a reference file (e.g. references/delta-spec-format.md) referenced from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Most of the body is operational guidance that earns its tokens, but the orchestrator gate plus the "Executor Override" section restate the same point, and the "Language Domain Contract" is verbose about register conventions Claude could infer, so it could be tightened.	2 / 3
Actionability	It provides exact file paths, directory trees, and copy-paste-ready markdown templates for ADDED/MODIFIED/REMOVED/RENAMED delta sections plus a return-summary template, giving fully executable guidance.	3 / 3
Workflow Clarity	Six numbered steps are clearly sequenced with explicit MANDATORY persistence markers and a CRITICAL copy-full-then-edit pitfall-avoidance workflow for MODIFIED requirements, supplying concrete checkpoints even without a validate-retry loop.	3 / 3
Progressive Disclosure	Sections are well-organized and reference one-level-deep shared files (skills/_shared/sdd-phase-common.md, openspec-convention.md) with clear section pointers, but substantial detail (full delta-spec templates, RFC 2119 table, all six steps) lives inline in SKILL.md with no bundle files to offload it.	2 / 3
	Total	10 / 12 Passed

Description

75%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, specific to a clear niche, and explicitly pairs capability with an explicit trigger clause. It is held back from full marks by a single-verb action list and trigger phrasing framed as internal orchestrator jargon rather than natural user terms.

Suggestions

Add a second concrete verb to broaden the action list, e.g. "Write and refine SDD delta specs with requirements and scenarios".

Reframe the trigger in natural user/orchestrator terms, e.g. "Use when the orchestrator needs to turn a proposal into delta specs (requirements + Given/When/Then scenarios)."

Dimension	Reasoning	Score
Specificity	"Write SDD delta specs with requirements and scenarios" names the domain and the deliverable components (delta specs, requirements, scenarios), but relies on a single verb rather than listing multiple distinct concrete actions as the top anchor requires.	2 / 3
Completeness	It explicitly answers both what ("Write SDD delta specs with requirements and scenarios") and when ("Trigger: orchestrator launches spec work for a change"), with an explicit trigger clause equivalent to a 'Use when...' guidance.	3 / 3
Trigger Term Quality	"Trigger: orchestrator launches spec work for a change" contains relevant terms (spec work, change) but the phrasing is system-internal orchestrator jargon rather than natural language a user would say, so it has some keywords but misses common variations.	2 / 3
Distinctiveness Conflict Risk	"SDD delta specs" carves out a clear niche tied to a specific spec-writing workflow with distinct triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
referenced_paths_exist	Referenced path issues: 2 missing, 2 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: Gentleman-Programming/gentle-ai
Path: internal/assets/skills/sdd-spec/SKILL.md
Commit: e01b114

Reviewed: about 14 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.