speckit-implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-implement/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 a well-sequenced, highly actionable implementation workflow with strong validation checkpoints and error handling, but it is over-long and monolithic, padding the context with a language-specific ignore-pattern catalog and duplicated hook instructions that belong in separate reference files.

Suggestions

Move the 'Common Patterns by Technology' and 'Tool-Specific Patterns' gitignore catalogs into a references file (e.g. IGNORE_PATTERNS.md) and link to it, keeping only the detection logic inline.

De-duplicate the extension-hook handling: define the before_implement/after_implement logic once and reference it from both Pre-Execution Checks and step 10 instead of repeating the full templates.

Extract the hook output templates into a references file so the main outline stays lean while the exact output formats remain one level deep.

Dimension	Reasoning	Score
Conciseness	The procedural core is efficient and actionable, but it pads the body with a 14-language plus tool-specific gitignore pattern catalog that Claude already knows, and duplicates the extension-hook handling instructions verbatim in both Pre-Execution Checks and step 10, fitting 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the lean level-3 anchor.	2 / 3
Actionability	It provides fully concrete, executable guidance: shell commands (git rev-parse, the powershell prerequisite script), checklist parsing regex, and copy-paste-ready hook output blocks, matching the 'fully executable code/commands; copy-paste ready' anchor and clearly above the pseudocode level-2 anchor.	3 / 3
Workflow Clarity	It lays out a clearly numbered 10-step sequence with explicit validation gates (checklist PASS/FAIL with STOP-and-ask, per-phase checkpoints, completion validation) and literally processes checklists for a complex process, satisfying the level-3 anchor of clear sequence with explicit validation and checklists.	3 / 3
Progressive Disclosure	Sections are well organized, but the skill is a large monolithic file with no bundle references and substantial reference material (the gitignore pattern catalog and hook output templates) inlined that should be split into separate files, matching 'some structure but content that should be separate is inline' rather than the appropriately-split level-3 anchor.	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 and ties it to a specific artifact (tasks.md), but it omits any explicit 'Use when...' trigger guidance and relies on somewhat generic action verbs, leaving every dimension at the middle level.

Suggestions

Append a 'Use when...' clause naming natural trigger phrases, e.g. 'Use when executing a spec-kit implementation plan or working through tasks in tasks.md'.

Replace generic verbs ('processing and executing') with more specific concrete actions the skill performs (e.g. 'runs prerequisite checks, validates checklists, executes phased tasks, and marks progress').

Add common user-facing trigger variations (e.g. 'implementation', 'execute the plan', 'run tasks') to improve natural keyword coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ("implementation plan", "tasks.md") and actions ("processing and executing all tasks") but does not list multiple distinct concrete actions, matching the 'names domain and some actions, but not comprehensive' anchor rather than the level-3 list of specific actions.	2 / 3
Completeness	It clearly states what the skill does ("Execute the implementation plan by processing and executing all tasks defined in tasks.md") but provides no 'Use when...' clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	It includes relevant keywords like "implementation plan" and "tasks" but relies on the filename "tasks.md" and lacks common natural variations users would say, fitting 'some relevant keywords but missing common variations' rather than full coverage.	2 / 3
Distinctiveness Conflict Risk	The tasks.md/spec-kit reference gives it a recognizable niche, but without distinct trigger phrases and with fairly generic verbs ("process/execute tasks") it could still overlap with other implement or task-management skills, matching the level-2 anchor.	2 / 3
	Total	8 / 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_version	'metadata.version' is missing	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: unoplatform/uno
Path: .claude/skills/speckit-implement/SKILL.md
Commit: 5927220

Reviewed: about 16 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.