spring-planning
Create structured implementation plan in docs/plans/
49
36%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/spring-planning/SKILL.mdQuality
Discovery
17%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 terse and lacks critical information for skill selection. It provides a single action without elaborating on what a 'structured implementation plan' entails, and completely omits any 'Use when...' guidance that would help Claude know when to select this skill over others.
Suggestions
Add a 'Use when...' clause with trigger terms like 'implementation plan', 'project plan', 'task breakdown', 'roadmap', 'planning a feature', or 'breaking down work'.
List specific concrete actions such as 'Breaks down features into phases, defines milestones, identifies dependencies, and creates step-by-step task lists in docs/plans/'.
Include natural keyword variations users might say, e.g., 'plan', 'planning', 'roadmap', 'design doc', 'architecture plan', 'project breakdown'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific action ('create structured implementation plan') and a specific location ('docs/plans/'), but does not list multiple concrete actions or elaborate on what the plan contains or how it's structured. | 2 / 3 |
Completeness | Provides a minimal 'what' (create a plan) but completely lacks a 'when' clause or any explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also quite thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Contains 'implementation plan' as a keyword, but lacks natural variations users might say such as 'project plan', 'roadmap', 'task breakdown', 'planning', 'architecture plan', or 'design doc'. The term 'docs/plans/' is a file path, not a natural trigger term. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'docs/plans/' directory adds some specificity, but 'implementation plan' is broad enough to overlap with general planning, documentation, or project management skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides an extremely thorough and actionable workflow for creating implementation plans, with excellent step sequencing and validation checkpoints. However, it suffers significantly from verbosity — testing requirements are repeated 5+ times, the inline plan template is enormous, and concepts Claude already understands are over-explained. The entire content would benefit greatly from splitting the plan template into a separate file and eliminating redundant instructions.
Suggestions
Extract the plan template (the large markdown block in step 2) into a separate PLAN_TEMPLATE.md file and reference it, reducing the main skill by ~60%
Consolidate the testing requirements into a single authoritative section instead of repeating them in Development Approach, Testing Strategy, task template comments, and execution enforcement
Remove explanatory text Claude already knows, such as what TDD means, how to create directories with mkdir -p, and the detailed explanation of what unit tests should cover
Trim the HTML comment block in the plan template — the example tasks are useful but the verbose guidelines above them duplicate what's already stated in Development Approach
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines. It over-specifies things Claude already knows (how to ask questions, what TDD means, how to create directories), includes lengthy HTML comments as template examples, and repeats testing requirements at least 5 times across different sections (Development Approach, Testing Strategy, task template comments, execution enforcement). The plan template alone is massive and could be a separate reference file. | 1 / 3 |
Actionability | The skill provides highly concrete, executable guidance: specific file naming conventions (yyyymmdd-<task-name>.md), exact markdown templates with structure, specific tool calls (AskUserQuestion, TodoWrite, mcp__ide__getDiagnostics), concrete example task structures with file paths, and precise JSON for the next-steps prompt. Everything is copy-paste ready. | 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, verify acceptance criteria), feedback loops (fix failures before proceeding, re-validate), and clear skip conditions (step 1.5 skip criteria, step 2.1 conditional execution). The execution enforcement section adds explicit rules for error recovery. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to offload content to. The massive plan template (which is the bulk of the content) should be in a separate template file. The task structure guidelines comment block, the example format for approaches, and the detailed testing strategy could all be referenced rather than inline. Everything is crammed into one file with no external references. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
100%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
4d8e766
- 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.