agile-product-owner

Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with concrete templates, worked examples, an executable script, and well-sequenced workflows that each end in a validation step. Its main weakness is conciseness: substantial content is duplicated between the inline sections and the reference files, and two asset files are bundled but never referenced.

Suggestions

Remove the inline material that is already covered in references/user-story-templates.md and references/sprint-planning-guide.md (e.g., story types, AC patterns, splitting techniques, capacity formula, velocity tracking, DoD), keeping the body as an overview that points to those files.

Either reference assets/sprint_planning_template.md and assets/user_story_template.md from the relevant sections or remove them from the bundle so there are no orphaned files.

Trim the 'What Makes This Skill Different' section or merge its concrete facts (40/30/15/15 weights, minimum AC counts) into the workflows they belong to, dropping the marketing framing.

Dimension	Reasoning	Score
Conciseness	Mostly efficient tables and templates, but inline content (story types, AC patterns, INVEST, splitting, capacity, velocity, DoD, metrics) duplicates what the reference files contain, and the 'Reference Documentation' section re-summarizes that same material, adding avoidable tokens.	3 / 5
Actionability	Fully actionable: concrete user-story and Given-When-Then templates with worked examples, a capacity calculation with numbers, sprint-loading templates, weighted prioritization factors, and an executable generator script with real commands and sample output.	5 / 5
Workflow Clarity	The three workflows are clearly numbered with an explicit validation step at the end of each, plus INVEST and Definition-of-Done checklists; held below 5 because there are no error-recovery feedback loops (the validations state what to check but not what to do on failure).	4 / 5
Progressive Disclosure	Good structure with a TOC, clear section headers, and one-level-deep references signaled inline ('See references/... for complete ...') plus a dedicated reference section; gaps are the inline duplication of reference-file content and two orphaned asset files never referenced from the body.	4 / 5
	Total	16 / 20 Passed

Description

96%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it concisely states what the skill does and gives a rich, natural 'Use when' trigger clause covering the core PO activities. The only soft spot is minor overlap with adjacent Scrum/PM skills on sprint-planning and velocity triggers.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions (user story writing, acceptance criteria, sprint planning, velocity tracking, story point estimation, epic breakdown, backlog prioritization) with comprehensive coverage of the domain, matching the 5 anchor.	5 / 5
Completeness	Explicitly answers both 'what' ('Agile product ownership for backlog management and sprint execution. Covers...') and 'when' ('Use when writing user stories...') with concrete trigger phrases, matching the 5 anchor exactly.	5 / 5
Trigger Term Quality	The 'Use when' clause enumerates natural PO phrases ('writing user stories', 'planning sprints', 'estimating story points', 'breaking down epics', 'prioritizing the backlog') that a user would actually say, giving comprehensive keyword coverage.	5 / 5
Distinctiveness Conflict Risk	Agile product ownership / backlog management is a clear niche with distinct triggers, but 'velocity tracking' and 'sprint planning' overlap with a Scrum Master skill, giving minor overlap risk rather than the minimal risk of a 5.	4 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: product-team/agile-product-owner/skills/agile-product-owner/SKILL.md
Commit: 19392f7

Reviewed: ~1 hour ago

Table of Contents

Discovery Implementation Validation

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.