implementation-approach

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

Quality

26%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/implementation-approach/SKILL.md

Quality

Discovery

32%

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

This description is too abstract and buzzword-heavy to be effective. It fails to describe concrete actions the skill performs and uses generic terms that would overlap with many other development-related skills. While it includes a 'Use when...' clause, the trigger terms are not natural user language and the capabilities remain unclear.

Suggestions

Replace 'implementation strategy selection framework' with specific concrete actions, e.g., 'Compares implementation approaches (e.g., iterative vs. big-bang), evaluates technical tradeoffs, and generates step-by-step development plans.'

Add natural trigger terms users would actually say, such as 'how to build', 'architecture decision', 'which approach', 'project planning', 'technical strategy'.

Narrow the scope to a distinct niche to reduce conflict risk—clarify what kind of implementation strategies (e.g., software migration, feature rollout, system redesign) and what distinguishes this from general coding or architecture skills.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'implementation strategy selection framework', 'development approach', and 'verification criteria' without listing any concrete actions. There are no specific capabilities described—no verbs indicating what the skill actually does (e.g., compare approaches, generate plans, evaluate tradeoffs).	1 / 3
Completeness	It has a 'Use when...' clause which addresses the 'when', but the 'what' is extremely weak—'implementation strategy selection framework' doesn't clearly explain what the skill does. The 'when' triggers are also vague and overlap heavily with the 'what'.	2 / 3
Trigger Term Quality	Terms like 'implementation strategy', 'development approach', and 'verification criteria' are somewhat relevant but overly generic and not natural phrases users would typically say. Users are more likely to say things like 'how should I build this', 'what architecture should I use', or 'plan my project'.	2 / 3
Distinctiveness Conflict Risk	Terms like 'implementation strategy', 'development approach', and 'planning' are extremely broad and would likely conflict with many other skills related to coding, architecture, project management, or software design. There is no clear niche carved out.	1 / 3
	Total	6 / 12 Passed

Implementation

20%

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

This skill is a high-level strategic framework that reads more like a consulting methodology than an actionable skill for Claude. It is extremely verbose, almost entirely abstract, and provides no concrete examples, templates, or executable guidance. While the phased structure provides some organizational clarity, the content fails to leverage Claude's existing knowledge and doesn't provide the specific, actionable instructions needed for effective skill execution.

Suggestions

Replace abstract YAML category lists with concrete, filled-in examples showing what a completed analysis or decision looks like for a real scenario (e.g., a sample migration decision with actual trade-offs documented).

Add a concrete output template or example design doc that Claude should produce when applying this framework, so the skill has a clear deliverable.

Cut at least 50% of the content by removing meta-cognitive framing and category labels that Claude already understands (e.g., 'Risk Analysis Matrix' categories like 'Technical Risks: System impact, data consistency...' are obvious to Claude).

Add a quick-start section with a condensed decision tree or flowchart (e.g., 'If migrating existing system → start Phase 1 → if high risk → use Strangler Pattern') to make the workflow immediately actionable.

Dimension	Reasoning	Score
Conciseness	Extremely verbose and abstract. Most content describes high-level frameworks and meta-cognitive processes that Claude already understands. YAML blocks contain vague category labels rather than actionable content. The skill reads like a consulting methodology document rather than a concise skill file.	1 / 3
Actionability	Almost entirely abstract and descriptive with no concrete code, commands, or executable examples. Phrases like 'Comprehensive Current State Analysis' and 'Strategy Exploration and Creation' describe what to think about rather than what to do. No copy-paste ready artifacts, templates, or specific outputs are provided.	1 / 3
Workflow Clarity	The six phases provide a clear sequence, and the progression from analysis to documentation is logical. However, there are no validation checkpoints or feedback loops between phases, and the steps within each phase are abstract checklists rather than concrete actions with verification criteria.	2 / 3
Progressive Disclosure	The content is structured with clear headings and phases, which aids navigation. However, it's a monolithic document with no references to external files for detailed content (e.g., strategy pattern details, risk matrix templates). The inline YAML blocks add bulk that could be separated.	2 / 3
	Total	6 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: shinpr/claude-code-workflows
Commit: 2e719be

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