agile-product-owner
Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing backlog.
85
71%
Does it follow best practices?
Impact
94%
1.13xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./product-team/agile-product-owner/SKILL.mdQuality
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 clearly defines its domain (agile product ownership), lists specific capabilities, and provides explicit trigger guidance via a 'Use for...' clause. It uses appropriate third-person voice and includes a comprehensive set of natural trigger terms that practitioners would use. The description is concise yet thorough, making it easy for Claude to select this skill when appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: user story writing, acceptance criteria, sprint planning, velocity tracking, estimating story points, breaking down epics, and prioritizing backlog. | 3 / 3 |
Completeness | Clearly answers both 'what' (backlog management, sprint execution, user story writing, acceptance criteria, sprint planning, velocity tracking) and 'when' with an explicit 'Use for...' clause listing specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'user stories', 'acceptance criteria', 'sprint planning', 'story points', 'epics', 'backlog', 'velocity tracking'. These are terms practitioners naturally use when seeking help with agile product ownership. | 3 / 3 |
Distinctiveness Conflict Risk | Occupies a clear niche around agile product ownership with distinct domain-specific triggers like 'user stories', 'story points', 'epics', 'sprint planning', and 'backlog' that are unlikely to conflict with non-agile skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured with good progressive disclosure and clear section organization, but suffers significantly from verbosity—it extensively explains standard agile concepts that Claude already knows (INVEST, Given-When-Then, Fibonacci estimation, sprint ceremonies). The actionability is moderate; templates are provided but much content is descriptive rather than providing novel, executable guidance. The skill would benefit greatly from being cut to perhaps 30% of its current length, focusing only on project-specific conventions or non-obvious patterns.
Suggestions
Remove explanations of standard agile concepts Claude already knows (INVEST criteria definitions, Given-When-Then format explanation, priority level definitions, persona types) and focus only on project-specific conventions or non-obvious patterns.
Cut the content by 60-70%: keep only the templates, the tool usage commands, and any project-specific standards; move reference tables to the referenced markdown files.
Strengthen validation steps with concrete feedback loops—e.g., 'If a story exceeds 8 points, apply splitting technique X; if acceptance criteria aren't testable, rewrite using pattern Y'.
Make the sample tool output more realistic with domain-specific acceptance criteria rather than generic placeholders like 'Given user has access, When they view key metrics, Then the result is displayed'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with extensive tables and templates that explain concepts Claude already knows well (agile methodology, INVEST criteria, Given-When-Then format, Fibonacci estimation). The persona reference table, availability factors, and priority level definitions are all standard agile knowledge that don't need to be spelled out. | 1 / 3 |
Actionability | The skill provides templates and examples that are somewhat actionable (user story format, sprint loading template, capacity calculation), but much of it is descriptive rather than instructive. The tool script references (python scripts/user_story_generator.py) add concreteness, but the sample output shows generic/placeholder acceptance criteria that aren't particularly useful as guidance. | 2 / 3 |
Workflow Clarity | Each workflow section has numbered steps with a validation checkpoint at the end, which is good. However, the validation steps are superficial ('Story passes all INVEST criteria') rather than providing concrete feedback loops for what to do when validation fails. The workflows are more like checklists than true step-by-step processes with error recovery. | 2 / 3 |
Progressive Disclosure | The skill has a clear table of contents, well-organized sections, and appropriately references external files (references/user-story-templates.md, references/sprint-planning-guide.md) for deeper content. Navigation is straightforward with one-level-deep references clearly signaled. | 3 / 3 |
Total | 8 / 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
- alirezarezvani/claude-skills
- Commit
f567c61
- 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.