planner
Create comprehensive, phased implementation plans with sprints and atomic tasks. Use when user says: "make a plan", "create a plan", "plan this out", "plan the implementation", "help me plan", "design a plan", "draft a plan", "write a plan", "outline the steps", "break this down into tasks", "what's the plan for", or any similar planning request. Also triggers on explicit "/planner" or "/plan" commands.
87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
92%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 is a strong skill description that excels at trigger term coverage and completeness. It clearly defines what the skill produces (phased implementation plans with sprints and atomic tasks) and provides extensive natural language triggers. The main weakness is potential overlap with other planning or task-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'comprehensive, phased implementation plans with sprints and atomic tasks' - describes the structure and granularity of outputs clearly. | 3 / 3 |
Completeness | Clearly answers both what (create phased implementation plans with sprints and atomic tasks) AND when (explicit 'Use when user says:' clause with comprehensive trigger examples). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger phrases users would say: 'make a plan', 'create a plan', 'plan this out', 'break this down into tasks', 'outline the steps', plus command triggers '/planner' and '/plan'. | 3 / 3 |
Distinctiveness Conflict Risk | While planning-focused, phrases like 'break this down into tasks' and 'outline the steps' could overlap with task management or project breakdown skills. The 'implementation plans' focus helps but isn't fully distinctive. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured planning skill with clear workflow phases, good validation checkpoints, and actionable examples. The main weaknesses are moderate verbosity in the question categories and inline template that could be externalized. The good/bad task examples effectively demonstrate expectations.
Suggestions
Move the plan template to a separate file (e.g., PLAN_TEMPLATE.md) and reference it to reduce inline bulk
Trim the 10 question categories to 3-4 key areas or simply instruct Claude to 'ask 5-10 clarifying questions prioritizing ambiguity and risk reduction' without exhaustive examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., listing 10 example question categories when Claude can infer appropriate questions). The template section is verbose and could be trimmed. | 2 / 3 |
Actionability | Provides concrete, specific guidance with clear examples (good vs bad task breakdown), explicit file naming conventions, and a complete template. The process steps are executable and copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear phased sequence (Research → Clarify → Docs → Create → Save → Gotchas) with explicit validation checkpoints (demo/verification checklists, gotcha review after save). Includes feedback loop for refinement based on gotchas. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but the full plan template is inline rather than referenced externally. For a skill of this length (~120 lines), the template could be split to a separate file to improve scannability. | 2 / 3 |
Total | 10 / 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.
- 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.