dev-implementation

AI DevKit · Implementation phase guidance for executing feature plans and checking implementation against design. Use when the user wants to implement planned tasks, update implementation docs, verify code matches design, or run dev-lifecycle phases 5 and 7.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/dev-implementation/SKILL.md

Quality

Content

75%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 is a well-structured, mostly lean implementation workflow with concrete commands, clear sequencing, and good section navigation. It loses points mainly for a few abstract directives and implicit (rather than explicit) validate-fix-retry feedback loops on destructive steps.

Suggestions

Make validation feedback loops explicit for destructive steps: e.g., after running `npx ai-devkit@latest lint`, add a 'if lint fails: fix issues and re-run before proceeding' branch.

Tighten abstract directives like "Model the domain when implementation friction repeats" into a concrete trigger and action (what friction pattern, what smallest structure, how to verify the fit).

Since Check Implementation reviews files for issues, add an explicit checklist item to re-run `lint` after edits so the validation checkpoint is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and imperative throughout with no padding or explanation of concepts Claude already knows; held at 4 rather than 5 because a few directives (e.g., "Model the domain when implementation friction repeats") are abstract rather than maximally tight.	4 / 5
Actionability	Provides concrete commands ("npx ai-devkit@latest lint", "npx ai-devkit@latest lint --feature <name>"), concrete file-resolution paths, and concrete status tokens; as an instruction-only skill most guidance is actionable, though several steps remain high-level directives rather than copy-paste actions.	4 / 5
Workflow Clarity	Both Execute Plan and Check Implementation are clearly sequenced numbered lists with Phase Contract prerequisites, lint-based validation checkpoints, and "Next:" handoff transitions; not a 5 because validation feedback loops (validate -> fix -> retry) are implicit rather than spelled out for the destructive code-change steps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections (Phase Contract, Execute Plan, Check Implementation) with explicit "Next:" navigation and no unnecessary nesting; no bundle files exist, so structure is purely inline and well placed, though it lacks the one-level-deep references that would reach 5.	4 / 5
	Total	16 / 20 Passed

Description

83%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 is strong: it states concrete capabilities, includes an explicit "Use when..." trigger clause with natural phrases and phase numbers, and is clearly scoped to the AI DevKit implementation phase. The main gap is that the action verbs lean slightly abstract and a few trigger synonyms are missing.

Dimension	Reasoning	Score
Specificity	Names the implementation domain plus several concrete actions ("executing feature plans", "checking implementation against design", "implement planned tasks", "update implementation docs", "verify code matches design"); not a 5 because the verbs are somewhat abstract and not fully enumerated.	4 / 5
Completeness	Explicitly answers both what (implementation phase guidance for executing plans and checking against design) and when (a concrete "Use when..." clause with multiple triggers), matching the anchor for clearly answering both.	5 / 5
Trigger Term Quality	The "Use when the user wants to implement planned tasks, update implementation docs, verify code matches design, or run dev-lifecycle phases 5 and 7" clause covers natural phrases plus explicit phase numbers; a few common synonyms are missing, so it stops short of 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to "AI DevKit · Implementation phase" with specific phase numbers (5 and 7), giving it a clear niche and low conflict risk; held at 4 due to residual overlap with sibling dev-lifecycle skills.	4 / 5
	Total	17 / 20 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: codeaholicguy/ai-devkit
Path: skills/dev-implementation/SKILL.md
Commit: d56e554

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.