implementation-approach

Implementation strategy selection framework. Use when planning implementation strategy, selecting development approach, or defining verification criteria.

Quality

59%

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/implementation-approach/SKILL.md

Quality

Content

60%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-sequenced, structured decision framework with clear phase ordering and checkpoints, but it is conceptual and verbose rather than executable, offering no code or concrete examples. Conciseness and actionability are the main weaknesses.

Suggestions

Add a short worked example (a brief before/after scenario showing one phase producing a Selected Design) so the abstract convergence steps become concrete and actionable.

Tighten Phase 2 and Phase 3 prose, since the total-complexity comparison and 'start with the direct strategy' guidance are restated across phases and could be consolidated.

Consider moving the reference strategy-pattern catalogs (Legacy/New Development/Integration) into a references file and summarizing only the selection rule inline, reducing body length.

Dimension	Reasoning	Score
Conciseness	The body is mostly dense and procedural without padding concepts Claude already knows, but several passages are abstract and repetitive (e.g., the convergence and subtraction prose restates the same total-complexity idea across multiple phases) and could be tightened.	3 / 5
Actionability	It gives concrete decision criteria and named patterns (Strangler, Facade, Vertical/Horizontal Slice, L1/L2/L3) but provides no executable code, commands, or worked before/after examples — guidance is conceptual instruction rather than copy-paste ready steps.	3 / 5
Workflow Clarity	The seven phases are clearly sequenced with an explicit ordering directive ('Complete these steps in order') and a Quality Checks section plus subtraction/evidence checkpoints; it lacks a validate-fix-retry feedback loop but the operations are decision-making rather than destructive or batch execution.	4 / 5
Progressive Disclosure	Content is well-structured into clearly headed phases and supporting sections (Verification Levels, Integration Points, Quality Checks) with no external bundle files needed and no nested references, though the single-file monolith is long and some pattern catalogs could live in references.	4 / 5
	Total	14 / 20 Passed

Description

58%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 covers both what and when in third person, but is generic and self-referential, repeating the title jargon as its triggers rather than offering concrete, user-natural phrasings. It is competent but not distinctive.

Suggestions

Replace generic planning verbs with concrete actions the skill performs (e.g., 'selects between vertical-slice, horizontal-slice, and hybrid implementation approaches and documents the chosen strategy and verification level').

Add user-natural trigger phrases beyond the title, such as 'Use when deciding how to sequence implementation work, choosing vertical vs horizontal slices, or defining L1/L2/L3 verification criteria'.

Tighten distinctiveness by naming the decision artifact produced (e.g., 'records the selected strategy and its total-complexity basis in an implementation or design decision record').

Dimension	Reasoning	Score
Specificity	Names the domain ('Implementation strategy selection framework') but the only concrete actions offered are 'planning implementation strategy, selecting development approach, or defining verification criteria' — generic planning verbs rather than discrete concrete operations.	3 / 5
Completeness	It explicitly states both what ('Implementation strategy selection framework') and when ('Use when planning implementation strategy, selecting development approach, or defining verification criteria'), though the 'when' clause reuses the title words rather than giving fresh concrete triggers.	4 / 5
Trigger Term Quality	The 'Use when' phrase ('planning implementation strategy, selecting development approach, or defining verification criteria') is somewhat natural but repeats the title jargon and omits common phrasings users would say (e.g., 'how should I build this', 'vertical vs horizontal slice').	3 / 5
Distinctiveness Conflict Risk	'Implementation strategy selection' is a recognizable niche but the phrasing is abstract and could overlap with general planning, design, or architecture-decision skills, leaving moderate conflict risk.	3 / 5
	Total	13 / 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: shinpr/claude-code-workflows
Path: skills/implementation-approach/SKILL.md
Commit: 9b7f687

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