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 third person voice appropriately and includes comprehensive natural language trigger terms that practitioners would use. The description is concise yet thorough, making it easy for Claude to distinguish this skill from others.
| 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' (agile product ownership covering 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. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to agile product ownership and sprint execution with distinct domain-specific triggers like 'story points', 'epics', 'backlog', and 'sprint planning' that are unlikely to conflict with other 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, persona types). 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 ~30% of its current size, focusing only on project-specific conventions or non-obvious patterns.
Suggestions
Drastically reduce content by removing explanations of standard agile concepts Claude already knows (INVEST criteria definitions, what Given-When-Then is, persona types, story point scales) and focus only on project-specific conventions or non-obvious patterns.
Make validation steps more actionable with explicit feedback loops, e.g., 'If story exceeds 8 points → apply splitting technique from table → re-estimate → re-validate' rather than just stating the check.
Replace generic acceptance criteria examples in the sample output with higher-quality, domain-specific examples that demonstrate the difference between good and bad criteria.
Consolidate the many reference tables (persona reference, story types, availability factors) into the referenced external files to keep the main skill lean.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with extensive tables and templates that explain basic agile concepts Claude already knows well (INVEST criteria, Given-When-Then format, Fibonacci estimation, persona types). Much of this is standard agile methodology that doesn't need to be spelled out in detail. | 1 / 3 |
Actionability | The skill provides templates and examples that are somewhat actionable (story templates, sprint loading format), but much of the guidance is procedural description rather than executable. The Python script references are concrete 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') and there are no feedback loops for when validation fails—just a single check at the end of each workflow rather than iterative correction steps. | 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. | 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
a96cc20
- 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.