spring-planning

Create structured implementation plan in docs/plans/

Quality

43%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/spring-planning/SKILL.md

Quality

Content

55%

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

The skill provides excellent actionability with concrete tools, templates, and decision logic, and has a well-structured multi-step workflow with proper validation checkpoints. However, it is severely undermined by extreme verbosity — testing requirements are repeated 4+ times across different sections, the plan template is enormous and inlined, and the overall length (~300+ lines) wastes significant context window. The content desperately needs to be split across multiple files with the SKILL.md serving as an overview.

Suggestions

Extract the plan markdown template (the ~100-line code block in step 2) into a separate PLAN_TEMPLATE.md file and reference it from the skill body.

Consolidate the testing requirements into a single authoritative section instead of repeating them in Development Approach, Testing Strategy, task structure guidelines comment, execution enforcement, and individual task descriptions.

Move the persistence stack detection logic (step 2.1) into a separate reference file since it's a conditional sub-workflow that adds significant length.

Remove explanatory commentary that Claude doesn't need — e.g., the HTML comment block explaining task structure guidelines could be a brief reference to a TASK_GUIDELINES.md file.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines. It includes extensive template boilerplate, repeated emphasis on testing rules (stated in Development Approach, Testing Strategy, task structure guidelines, execution enforcement, and individual task templates), and explains concepts Claude already knows (what TDD is, how to mark checkboxes). The plan template alone is massive and could be a separate reference file. Many rules are restated 3-4 times.	1 / 3
Actionability	The skill provides highly concrete, executable guidance: specific file naming conventions (yyyymmdd-<task-name>.md), exact markdown template structure, specific tool calls (AskUserQuestion with JSON format, mcp__ide__getDiagnostics), concrete examples of task structure with file paths, and clear decision tables (persistence stack detection). The commit message format and directory structure are all specified.	3 / 3
Workflow Clarity	The multi-step workflow is clearly sequenced (steps 0 through 3 plus step 1.5 and 2.1) with explicit validation checkpoints: tests must pass before next task, plan review before implementation, approach selection before plan creation. Feedback loops are well-defined (fix tests → re-run → proceed). The execution enforcement section provides clear rules for error recovery and progress tracking.	3 / 3
Progressive Disclosure	This is a monolithic wall of text with no references to external files despite being extremely long. The massive plan template (100+ lines of markdown) should be in a separate template file. The persistence stack detection table, execution enforcement rules, and the plan structure template all could be split into referenced files. No bundle files are provided to support this content, and everything is inlined into a single enormous skill file.	1 / 3
	Total	8 / 12 Passed

Description

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.

The description is too terse, providing only a minimal action and output location without explaining what constitutes a 'structured implementation plan' or when Claude should select this skill. It lacks trigger terms, a 'Use when' clause, and detail about the plan's contents or structure.

Suggestions

Add a 'Use when...' clause with trigger terms like 'plan', 'implementation plan', 'project plan', 'break down tasks', 'roadmap', 'feature planning'.

Expand the 'what' portion to describe concrete actions, e.g., 'Breaks down features into phases, defines tasks with dependencies, estimates effort, and outputs a structured markdown plan in docs/plans/'.

Include natural keyword variations users might say, such as 'project planning', 'task breakdown', 'development plan', 'sprint planning'.

Dimension	Reasoning	Score
Specificity	Names a specific action ('create structured implementation plan') and a specific location ('docs/plans/'), but doesn't elaborate on what the plan contains or what concrete steps are involved.	2 / 3
Completeness	Describes what it does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also quite thin, warranting a 1.	1 / 3
Trigger Term Quality	Includes 'implementation plan' which is a natural term users might say, but misses common variations like 'project plan', 'roadmap', 'task breakdown', 'planning', or 'architecture plan'.	2 / 3
Distinctiveness Conflict Risk	The specific output location 'docs/plans/' adds some distinctiveness, and 'implementation plan' is somewhat specific, but it could overlap with general planning, documentation, or project management skills.	2 / 3
	Total	7 / 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: Amplicode/spring-skills
Commit: a77120d

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.