spring-planning

Create structured implementation plan in docs/plans/

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/spring-planning/SKILL.md

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 skill body is a well-sequenced, highly actionable planning workflow with strong validation gates and feedback loops. Its main weaknesses are repeated testing guidance across sections and a large inlined plan template that could live in a separate reference file.

Suggestions

Move the full plan template (lines 103-242) into a references file (e.g. references/plan-template.md) and link to it, keeping only a brief structural sketch inline to improve progressive disclosure.

Consolidate the testing rules into a single section and reference it from Development Approach and Testing Strategy to reduce repetition.

Tighten the HTML comment task-structure guidance, which duplicates the checklist rules already stated in the Development Approach section.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but testing requirements are restated across the Development Approach, Testing Strategy, and HTML-comment template sections, adding repetition that could be tightened.	3 / 5
Actionability	It provides concrete, executable guidance — named MCP tools, a copy-paste AskUserQuestion JSON, a dependency-detection table, and a full plan template — with only minor gaps (e.g. placeholders like '<project test command>').	4 / 5
Workflow Clarity	Steps are clearly sequenced (0 through 3 plus execution enforcement) with explicit validation checkpoints ('tests must pass before next task') and feedback loops ('if tests fail: fix before proceeding'), matching the score-5 anchor.	5 / 5
Progressive Disclosure	Structure is well organized with clear sections and signaled sibling-skill references, but no bundle files exist and a ~140-line plan template is inlined in SKILL.md rather than offloaded to a reference file, fitting the score-3 anchor of content that should be separate being inline.	3 / 5
	Total	15 / 20 Passed

Description

53%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 concise and states a clear action with a concrete output location, but it omits any 'when to use' trigger guidance, which caps completeness. It is reasonably distinct but could be stronger with natural trigger phrases.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to plan a feature, bug fix, refactor, or migration.'

Include synonyms users would naturally say (e.g. 'plan', 'planning', 'task plan') alongside 'implementation plan' to broaden trigger coverage.

Optionally list 1-2 more concrete actions (e.g. 'gather context interactively and propose approaches') to lift specificity toward a 4-5.

Dimension	Reasoning	Score
Specificity	Names the domain ('implementation plan') and one concrete action ('create structured implementation plan in docs/plans/'), matching the score-3 anchor of domain plus 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	The 'what' is clear (create a structured implementation plan), but there is no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	'implementation plan' and 'docs/plans/' are relevant terms a user might say, but common synonyms ('plan', 'planning', 'task plan') are missing, matching the score-3 anchor of some relevant keywords lacking common variations.	3 / 5
Distinctiveness Conflict Risk	The specific 'docs/plans/' output location anchors a fairly distinct niche with only minor overlap against general dev-planning skills, fitting the score-4 anchor of mostly distinct with minor overlap risk.	4 / 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: Amplicode/spring-skills
Path: skills/spring-planning/SKILL.md
Commit: bf19b3c

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