task-planning
Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management.
87
82%
Does it follow best practices?
Impact
98%
1.68xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, includes natural trigger terms from agile/scrum methodology, explicitly states both what it does and when to use it, and occupies a clear niche in software development planning that distinguishes it from coding or documentation skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'breaking down features', 'creating user stories', 'planning sprints', 'task breakdown', 'acceptance criteria', and 'backlog management'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Plan and organize software development tasks', 'task breakdown, user stories, acceptance criteria, backlog management') AND when ('Use when breaking down features, creating user stories, or planning sprints') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'features', 'user stories', 'sprints', 'task breakdown', 'acceptance criteria', 'backlog'. These are common terms in software development planning that users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on software development planning/agile methodology. The specific triggers like 'user stories', 'sprints', 'acceptance criteria', and 'backlog' are distinct to this domain and unlikely to conflict with general coding or documentation skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable templates for task planning with good concrete examples. However, it's overly verbose with explanations Claude doesn't need (INVEST definitions, basic agile concepts), lacks validation checkpoints in the workflow, and includes empty placeholder sections that waste tokens. The content would benefit from trimming explanatory text and adding verification steps.
Suggestions
Remove the INVEST acronym explanation and other basic agile concepts Claude already knows - just reference them by name
Add validation checkpoints: e.g., 'Review story against INVEST - if any criterion fails, revise before proceeding'
Delete the empty 'Examples' section placeholders and the Metadata section which adds no instructional value
Move the detailed templates (user story, sprint planning) to separate reference files and keep SKILL.md as a concise overview
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful templates but is verbose with redundant explanations. The INVEST acronym explanation is unnecessary (Claude knows this), and the extensive boilerplate examples could be condensed. The metadata section and empty example placeholders add no value. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready templates for user stories, sprint planning, and task decomposition. The markdown templates are complete and executable with specific fields, examples, and clear structure that Claude can directly apply. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Step 1-4), but lacks validation checkpoints. No guidance on verifying story quality, reviewing estimates, or iterating when stories don't meet INVEST criteria. The workflow is linear without feedback loops for refinement. | 2 / 3 |
Progressive Disclosure | Content is reasonably structured with clear sections, but everything is inline in one large file. The extensive templates and examples could be split into separate reference files. External links are provided but internal progressive disclosure is missing. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
Total | 10 / 11 Passed | |
- Repository
- supercent-io/skills-template
- Commit
c033769
- 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.