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.
69
84%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
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 clearly communicates what the skill does and when to use it. The extensive list of trigger phrases is a notable strength, covering many natural ways users request planning. The only weakness is moderate overlap risk with other task/project management skills, though the specificity around 'phased implementation plans with sprints and atomic tasks' helps mitigate this.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'comprehensive, phased implementation plans with sprints and atomic tasks.' This clearly describes the output format and structure (phases, sprints, atomic tasks). | 3 / 3 |
Completeness | Clearly answers both 'what' (create comprehensive, phased implementation plans with sprints and atomic tasks) and 'when' (explicit 'Use when...' clause with extensive trigger phrases and commands). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'make a plan', 'create a plan', 'plan this out', 'break this down into tasks', 'outline the steps', plus slash commands '/planner' and '/plan'. These are highly natural phrases. | 3 / 3 |
Distinctiveness Conflict Risk | While the planning niche is reasonably specific, terms like 'break this down into tasks' and 'outline the steps' could overlap with task management, project management, or general breakdown skills. The focus on 'phased implementation plans with sprints' helps distinguish it, but 'planning' is a broad concept. | 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 strong actionability and clear workflow sequencing across defined phases. The good/bad task examples and complete plan template provide excellent concrete guidance. Minor weaknesses include some verbose sections (the 10 question categories, the 'Important' reminders) and the inline template that could be split into a separate reference file for better progressive disclosure.
Suggestions
Trim the 10 question categories to 3-4 key areas or simply say 'Ask 5-10 clarifying questions prioritizing ambiguity and risk reduction' — Claude can generate appropriate questions without the exhaustive list.
Move the plan template to a separate file (e.g., PLAN_TEMPLATE.md) and reference it from the main skill to improve progressive disclosure and reduce inline bulk.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary padding like the exhaustive list of 10 question categories (goals, scope, users, platforms, etc.) that Claude can infer, and the 'Important' section restates things Claude already knows. The template section is lengthy but arguably necessary as a reference. | 2 / 3 |
Actionability | Provides concrete, specific guidance throughout: clear bad/good task examples, a complete markdown template with exact structure, specific filename generation rules with examples, and explicit phase-by-phase instructions. The plan template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear multi-phase sequence (Research → Clarify → Docs → Create → Save → Gotchas) with explicit validation checkpoints: the gotchas phase serves as a feedback loop after saving, sprint requirements mandate demoable/testable increments, and each task requires validation methods. The workflow is well-sequenced with dependencies between phases. | 3 / 3 |
Progressive Disclosure | The skill is a single monolithic file with the full plan template inline. The template (~30 lines) could be a separate referenced file. References to 'Context7 skill' are mentioned but not linked. For a skill of this length (~120 lines), some content separation would improve navigation, though the section headers provide reasonable structure. | 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.
- Repository
- am-will/codex-skills
- Commit
d3983b1
- 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.