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
84%
Does it follow best practices?
Impact
Pending
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 it does (phased implementation plans with sprints and atomic tasks) and provides extensive explicit trigger guidance. The generous list of natural trigger phrases is a major strength. The only weakness is moderate overlap risk with other planning or task-management skills, though the specificity around '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 user says...' 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 users would actually use. | 3 / 3 |
Distinctiveness Conflict Risk | While the planning niche is fairly specific, terms like 'break this down into tasks' or 'outline the steps' could overlap with task management or project breakdown skills. The focus on 'phased implementation plans with sprints' helps distinguish it, but 'planning' is a broad concept that could conflict with other planning-adjacent skills. | 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 distinct phases. The good/bad task examples and the complete plan template provide excellent concrete guidance. Minor weaknesses include some verbosity in the question categories section and the inlined template that could be referenced separately.
Suggestions
Consider moving the full plan template to a separate file (e.g., PLAN_TEMPLATE.md) and referencing it to reduce inline bulk
Trim the 10 question categories in Phase 1 - Claude can generate contextually appropriate questions without an exhaustive list of categories
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary verbosity - the numbered question categories in Phase 1 could be trimmed, and some instructions like 'Think of 5-10 questions' are somewhat padded. The template section is useful but adds bulk. | 2 / 3 |
Actionability | Provides concrete, specific guidance throughout: clear good/bad task examples, a complete markdown template, specific filename generation rules, and explicit phase-by-phase instructions. The plan template is copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear multi-phase workflow (Phase 0-4) with logical sequencing, explicit validation checkpoints (Phase 4 gotchas review after saving, demo/verification checklists per sprint), and a feedback loop for refining the plan based on gotcha questions. | 3 / 3 |
Progressive Disclosure | Content is reasonably structured with clear phases and sections, but the full plan template is inlined rather than referenced from a separate file. The skill references 'Context7 skill' without linking to it. For a skill of this length (~100 lines), some content could be split out. | 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
ca2c3b3
- 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.