sprint-prioritizer
Creates sprint plans, prioritizes product backlogs using RICE/MoSCoW/Kano frameworks, generates capacity plans, writes user stories with acceptance criteria, and produces stakeholder-ready roadmaps. Use when a user needs to prioritize features, score backlog items, plan a sprint, groom stories, allocate team capacity, calculate story points, create a release roadmap, run RICE scoring, evaluate trade-offs between features, or prepare sprint review and retrospective materials.
88
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 an excellent skill description that clearly articulates specific capabilities using named frameworks and concrete deliverables, provides comprehensive trigger terms that match natural user language, and explicitly separates the 'what' from the 'when'. It uses proper third-person voice throughout and would be easily distinguishable from other skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creates sprint plans, prioritizes backlogs using named frameworks (RICE/MoSCoW/Kano), generates capacity plans, writes user stories with acceptance criteria, and produces stakeholder-ready roadmaps. | 3 / 3 |
Completeness | Clearly answers both 'what does this do' (first clause listing capabilities) AND 'when should Claude use it' with an explicit 'Use when...' clause containing a comprehensive list of trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'prioritize features', 'score backlog items', 'plan a sprint', 'groom stories', 'allocate team capacity', 'story points', 'release roadmap', 'RICE scoring', 'trade-offs between features', 'sprint review', 'retrospective'. These are all terms a product manager or scrum master would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche in product management and agile planning with highly specific triggers like RICE/MoSCoW/Kano frameworks, sprint planning, backlog grooming, and story points. Unlikely to conflict with generic project management or coding skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent concrete examples and templates that make sprint planning artifacts immediately producible. The main weakness is the lack of validation checkpoints in the workflow—there's no explicit step to confirm scoring assumptions with the user or verify that committed points fit capacity before proceeding. Minor verbosity could be trimmed but doesn't significantly detract from quality.
Suggestions
Add explicit validation checkpoints between steps, e.g., 'Confirm RICE scores with user before proceeding to capacity planning' and 'Verify total committed story points ≤ committable points before writing stories'.
Add a feedback loop for when total story points of prioritized items exceed sprint capacity (e.g., 'If committed items exceed 36 pts: drop lowest-RICE items or split stories until within budget').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient and well-structured, but includes some unnecessary explanation (e.g., 'All outputs are copy-paste ready' in the intro, explaining when to use alternative frameworks that Claude already understands). The capacity plan template and examples are useful but the overhead explanation ('standups, planning, review, retro, Slack') is somewhat verbose. | 2 / 3 |
Actionability | Highly actionable with concrete templates, filled-in examples (RICE table, capacity calculation, sprint goal, user story with acceptance criteria), and specific numbers. Every section provides copy-paste ready artifacts rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The 5-step workflow is clearly sequenced and logical, but lacks validation checkpoints. There's no step to verify the backlog scoring with the user, no checkpoint after capacity planning to confirm assumptions, and no feedback loop for when sprint commitment exceeds capacity. For a planning workflow where incorrect assumptions can cascade, explicit validation steps are needed. | 2 / 3 |
Progressive Disclosure | Well-organized with a clear overview, inline quick-reference sections for alternative frameworks, and a single-level reference to TEMPLATES.md for full copy-paste templates. Content is appropriately split between the main skill file and the companion file. | 3 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- OpenRoster-ai/awesome-agents
- Commit
010799b
- 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.