CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

speckit-implement

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./apps/reference/.claude/skills/speckit-implement/SKILL.md

The canonical home for this skill is speckit-implement in RihardsJ/software-factory

SKILL.md
Quality
Evals
Security

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.

The body delivers a strongly sequenced, highly actionable workflow with validation at every checkpoint — its workflow clarity is exemplary. Its weaknesses are token efficiency and organization: duplicated hook instructions and an inlined boilerplate pattern catalog that should live in a reference file inflate the skill's footprint without adding guidance value.

Suggestions

Extract the 'Common Patterns by Technology' and 'Tool-Specific Patterns' catalogs into a references/ file (e.g. references/ignore-patterns.md) and keep only the detection logic plus a pointer inline.

De-duplicate the extension-hook protocol: state the shared rules once and have the pre- and post-execution sections reference them, differing only in the hook key (before_implement vs after_implement) and output block.

Specify the Completion Report format (required fields such as tasks completed/failed per phase, checklist gate outcome, validation results) to close the main actionability gap.

DimensionReasoningScore

Conciseness

The core workflow is efficient and directive, but there is real trim: the ~40-line ignore-pattern catalog is boilerplate Claude largely knows, the hook protocol is duplicated nearly verbatim between the pre- and post-execution sections, and step 7's phase descriptions ('Implement models, services, CLI commands, endpoints') generically restate step 6. Not a 2 because nothing teaches concepts Claude doesn't know; not a 4 because the duplication and catalog are unnecessary tokens.

3 / 5

Actionability

Guidance is largely executable: the exact prerequisite script with flags ('check-prerequisites.sh --json --require-tasks --include-tasks'), precise checklist counting rules, exact status-table format, verbatim stop/ask wording, and copy-paste hook output templates. Not a 5 because the 'Completion Report' section is only 'Report final status with summary of completed work' with no format or required fields.

4 / 5

Workflow Clarity

The sequence is explicit (numbered Outline steps 1-9 with pre-execution checks, post-execution hooks, and a Done When checklist) and validation is present at every gate: the prerequisite check, the checklist STOP-and-ask gate, per-phase validation checkpoints, halt-on-failure error handling with retry reporting for parallel tasks, and completion validation against the spec and plan. Feedback loops and a closing checklist are both present.

5 / 5

Progressive Disclosure

Sections are well-headered and navigable, but no bundle files exist at all (no references/, scripts/, or assets/), and the inline technology-by-technology ignore-pattern catalog (~40 lines) is content that clearly belongs in a separate reference file. This is 'some structure, content that should be separate is inline'.

3 / 5

Total

15

/

20

Passed

Description

50%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.

The description clearly states what the skill does and anchors it to a concrete artifact (tasks.md), but it lacks any 'when to use' trigger guidance, natural synonyms, and spec-kit context that would distinguish it from generic implementation skills. It sits squarely at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to implement a spec, execute the plan, or run tasks from tasks.md in a spec-kit project.'

Enumerate the concrete actions the skill performs (verify checklists, execute tasks phase-by-phase following TDD, mark tasks [X], run extension hooks) instead of the circular 'execute by processing and executing'.

Mention the spec-kit/spec workflow context so the description is distinct from generic build or implementation skills.

DimensionReasoningScore

Specificity

The description names the target artifact ('all tasks defined in tasks.md') but its action is circular ('Execute the implementation plan by processing and executing all tasks'), offering only one concrete action without covering what execution involves (e.g., phase-by-phase task execution, marking tasks complete, checklist gating).

3 / 5

Completeness

The 'what' is clear (process and execute tasks defined in tasks.md), but there is no 'Use when...' clause or equivalent explicit trigger guidance; the rubric explicitly caps completeness at 3 in that case.

3 / 5

Trigger Term Quality

Relevant keywords like 'implementation plan', 'tasks', and 'execute' are present, but common variations a spec-kit user would naturally say — 'spec', 'speckit', 'implement the feature', 'build' — are missing, leaving keyword coverage partial.

3 / 5

Distinctiveness Conflict Risk

The tasks.md reference gives it a niche, but 'Execute the implementation plan' is generic plan-execution language that could overlap with other build or implementation skills, since no spec-kit context appears in the description.

3 / 5

Total

12

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

RihardsJ/software-factory

Path

apps/reference/.claude/skills/speckit-implement/SKILL.md

Reviewed

Table of Contents

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.