speckit-specify

Create or update feature specifications from natural language descriptions. Use when starting new features or refining requirements. Generates spec.md with user stories, functional requirements, and acceptance criteria following spec-driven development methodology.

Quality

81%

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

Quality

Content

70%Weight 40%Scale 1-5

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

A thorough, well-sequenced spec-generation workflow with strong validation feedback loops and concrete commands. Its main weaknesses are repetition that hurts token efficiency and heavy inlining of content that could be split into reference files.

Suggestions

Consolidate the duplicated [NEEDS CLARIFICATION] rules and clarification-priority guidance into a single location to remove repeated blocks and reduce tokens.

Move the full Specification Quality Checklist (step 6a) into a referenced checklist template file so SKILL.md stays a lean overview.

Fix the create-new-feature.ps1 invocation examples to use a single consistent flag style so the commands are unambiguously copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient but repeats the [NEEDS CLARIFICATION] and clarification-prioritization rules across step 4 and the 'For AI Generation' section, and includes an empty 'General Guidelines' header plus redundant guideline blocks that could be tightened.	3 / 5
Actionability	Provides mostly executable guidance — concrete git commands, template paths, and create-new-feature.ps1 invocations in both bash and PowerShell — though the mixed -Json/--json/-Number flag examples are slightly inconsistent.	4 / 5
Workflow Clarity	Presents a clear numbered sequence with explicit validation checkpoints in step 6 (Spec Quality Checklist, max-3-iteration feedback loop, [NEEDS CLARIFICATION] resolution) matching the anchor pattern for sequenced validation with error-recovery feedback.	5 / 5
Progressive Disclosure	No bundle files exist, so all detailed checklist and template content is inlined in SKILL.md; the structure is present but content that could live in separate files (e.g., the full requirements checklist) is kept inline rather than split out.	3 / 5
	Total	15 / 20 Passed

Description

92%Weight 40%Scale 1-5

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

A strong, specific description that clearly states both what it does and when to use it, with concrete deliverables and distinct triggers. Only minor room to add synonyms or file-extension cues for richer trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create or update feature specifications', 'Generates spec.md with user stories, functional requirements, and acceptance criteria' — giving comprehensive coverage of what the skill produces.	5 / 5
Completeness	Explicitly answers both 'what' (create/update specs, generate spec.md with stories/FRs/AC) and 'when' ('Use when starting new features or refining requirements') with concrete trigger phrasing.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'starting new features' and 'refining requirements' are present, but it omits common synonyms and lacks concrete file/extension cues, leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — spec-driven feature specification generation — with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: foryourhealth111-pixel/Vibe-Skills
Path: bundled/skills/speckit-specify/SKILL.md
Commit: ddcaa2a

Reviewed: 3 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.