CtrlK
BlogDocsLog inGet started
Tessl Logo

speckit-plan

Execute the implementation planning workflow using the plan template to generate design artifacts.

48

Quality

53%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/speckit-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is highly actionable with concrete commands and paths and is well-organized into clear sections, but it loses conciseness to near-verbatim duplication of the hook-processing logic and leaves the error-recovery feedback loop implicit. Tightening these would lift the weaker dimensions.

Suggestions

Factor the duplicated before_plan and after_plan hook-processing blocks into a single shared procedure referenced once, varying only the hook key and the optional/mandatory label wording.

Make the gate-failure error recovery explicit, e.g., 'on gate failure, document the violation, revise the design, then re-evaluate the Constitution Check until gates pass'.

Clarify the Phase 1 'Agent context update' step with the exact command or snippet that updates the CLAUDE.md markers, rather than describing the update in prose.

DimensionReasoningScore

Conciseness

The body is dense and free of concept-padding Claude already knows, but the before_plan and after_plan hook-processing blocks repeat ~95% identical text (~30 lines duplicated), which is a clear tightening opportunity.

2 / 3

Actionability

It gives concrete, executable guidance — exact script paths, JSON keys to parse, marker-delimited edit instructions, and a precise dot-to-hyphen transform — matching 'fully executable commands; copy-paste ready.'

3 / 3

Workflow Clarity

The outline and phases are clearly sequenced with prerequisites and gates, but the error-recovery loop is implicit: it says 'ERROR on gate failures' without specifying a fix-and-revalidate cycle, leaving a validation checkpoint gap.

2 / 3

Progressive Disclosure

The skill is a single self-contained file organized into clearly labeled sections with no nested or deep reference chains, and no bundle files exist to mis-signal, so organization alone supports a top score.

3 / 3

Total

10

/

12

Passed

Description

35%

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 clear about what the skill does but lacks explicit usage triggers and relies on jargon rather than natural keywords, weakening trigger-term quality and completeness. It identifies a specific niche but is not distinctive enough to prevent overlap.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases such as 'planning a feature', 'designing the implementation', or 'creating a plan for a spec'.

Replace jargon ('implementation planning workflow', 'design artifacts') with concrete, user-facing terms and list specific deliverables (e.g., data-model.md, contracts, research.md) to raise specificity.

Include common variations users might say (e.g., 'spec plan', 'feature plan') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain (implementation planning) and two verbs (execute workflow, generate design artifacts), but does not enumerate multiple specific concrete actions, so it stops at 'names domain and some actions, not comprehensive.'

2 / 3

Completeness

It clearly states the 'what' but provides no 'Use when...' or equivalent explicit trigger for when to use it, which per the guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

The phrasing uses technical jargon ('implementation planning workflow', 'plan template', 'design artifacts') rather than natural terms a user would actually say, matching 'no natural keywords; technical jargon or overly generic.'

1 / 3

Distinctiveness Conflict Risk

Implementation planning with a plan template is a recognizable niche, but without distinct trigger terms it could still overlap with other planning/spec skills.

2 / 3

Total

7

/

12

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.

Validation14 / 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
unoplatform/uno
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.