spec

Implement features using Spec Driven Development (SDD) workflow. Creates design and task documents with approval gates.

Quality

63%

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 ./.cursor/skills/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.

A well-sequenced, highly actionable planning workflow with explicit approval gates and copy-paste templates; its main weaknesses are a duplicated refine structure and the absence of any progressive disclosure via references. Overall a strong content body.

Suggestions

Consolidate the duplicated Step 2 and Step 3 "refine" blocks into a single reusable refinement procedure referenced by both steps to tighten conciseness.

Move the EARS pattern reference and/or the requirements.md / tasks.md example templates into a reference file linked one level deep from the main workflow to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean — templates and concrete artifacts rather than concept explanations — but the Step 2 and Step 3 "refine" blocks (scan / identify ambiguities / ask clarifying questions) duplicate near-identical language and could be consolidated.	2 / 3
Actionability	Concrete file paths (`.specs/{feature_name}/requirements.md`, `design.md`, `tasks.md`), named required sections, copy-paste-ready templates for requirements.md and tasks.md, the EARS pattern reference, and exact quoted approval-gate prompts give specific, actionable guidance.	3 / 3
Workflow Clarity	Seven ordered steps with "Do not skip steps", explicit approval-gate checkpoints (Steps 4 and 6), refine feedback loops ("Do not proceed until all critical ambiguities are resolved"), and a numbered checklist template match the clear-sequence-with-validation anchor.	3 / 3
Progressive Disclosure	Sections are well organized, but this is a single monolithic >50-line file with no references or file splits; the inline EARS patterns and example templates are separable material kept inline rather than behind one-level-deep references.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 clearly conveys what the skill does (planning/design documents with approval gates) but omits any explicit "when to use it" trigger guidance, leaving every dimension at the mid-anchor. Adding a "Use when..." clause with natural trigger terms would lift completeness and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to implement a feature, plan a feature, or start spec-driven / SDD work," to satisfy the missing "when" and raise completeness/distinctiveness.

Replace or supplement the jargon "Spec Driven Development (SDD) workflow" with natural phrasings users would actually say ("plan a feature", "write a spec", "design before coding").

Expand the action list beyond "Creates design and task documents with approval gates" to enumerate concrete deliverables (requirements doc, design doc, tasks checklist) for stronger specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (SDD) and concrete artifacts ("design and task documents", "approval gates", "Implement features"), but it is not a comprehensive multi-action list like the score-3 anchor ("Extract text..., fill forms, merge documents").	2 / 3
Completeness	The "what" is clearly stated, but there is no "Use when..." clause or equivalent explicit trigger, so per the judging guidelines completeness caps at 2.	2 / 3
Trigger Term Quality	"Implement features" is a natural user term, but "Spec Driven Development (SDD)" is methodology jargon and common variations ("spec", "design doc", "plan a feature") and explicit triggers are missing.	2 / 3
Distinctiveness Conflict Risk	SDD with approval gates is a recognizable niche, but the leading phrase "Implement features" is generic and there are no distinct explicit triggers, so it could overlap with general coding skills.	2 / 3
	Total	8 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: garden-co/classic-jazz
Path: .cursor/skills/spec/SKILL.md
Commit: 4f90501

Reviewed: 6 days 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.