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.
82
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/planner/SKILL.mdQuality
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 major strength, covering many natural ways users request planning. The only minor weakness is potential overlap with other task/project management skills, though the specificity of 'phased implementation plans with sprints and atomic tasks' helps differentiate it.
| 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 focus is clear, terms like 'break this down into tasks' and 'outline the steps' could overlap with general task management or project management skills. The specificity of 'phased implementation plans with sprints' helps but 'planning' is a broad domain. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid planning skill with a well-sequenced multi-phase workflow and good concrete examples (especially the bad vs good task breakdown). Its main weaknesses are the inlined template adding bulk, some verbosity in the question categories section, and the lack of executable tooling commands. The gotchas feedback loop is a strong design choice.
Suggestions
Move the plan template to a separate file (e.g., PLAN_TEMPLATE.md) and reference it to reduce inline bulk and improve scannability.
Add a concrete link or reference for the 'Context7 skill' mentioned in Phase 2, so Claude knows exactly how to invoke it.
Trim the 10 question categories to just the instruction 'Think of 5-10 questions prioritizing ambiguity and risk reduction' — Claude doesn't need example category names like 'Goals & success criteria' enumerated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary verbosity - the numbered question categories (1-10) are somewhat padded, and the template section is lengthy. However, most content earns its place by providing specific structure Claude wouldn't inherently know about the user's desired planning workflow. | 2 / 3 |
Actionability | Provides good structural guidance with concrete examples (bad vs good task breakdown, filename generation), but lacks executable code or commands. The plan template is concrete and copy-paste ready, but the process steps are more procedural descriptions than precise instructions with specific tool calls or commands. | 2 / 3 |
Workflow Clarity | Clear phased sequence (Research → Clarify → Docs → Create → Save → Gotchas) with explicit validation checkpoints: clarifying requirements before searching docs, demo/verification checklists per sprint, and a dedicated gotchas phase after saving that includes a feedback loop (ask questions → refine plan). The workflow is well-ordered with clear dependencies between phases. | 3 / 3 |
Progressive Disclosure | The content is reasonably well-structured with clear sections, but the full plan template is inlined rather than referenced from a separate file. The skill references a 'Context7 skill' without linking to it. For a skill of this length (~100 lines), the template could be split out to improve scannability. | 2 / 3 |
Total | 9 / 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
633b7e0
- 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.