agile-product-owner

Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills_all/agile-product-owner/SKILL.md

Quality

Content

65%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 concise and offers concrete commands, but it lacks any workflow sequence or validation for batch story generation, and it references a script file that is not present in the bundle. These gaps hold it at the midpoint on workflow clarity and progressive disclosure.

Suggestions

Add a short workflow with a verification checkpoint for batch story generation (e.g., generate -> review INVEST validation output -> refine -> finalize) so workflow clarity can exceed 3.

Provide the script's input contract (how epics are supplied) and a brief example output so the guidance is fully executable.

Either ship the referenced scripts/user_story_generator.py in a scripts/ bundle or remove the dangling reference, so progressive disclosure navigation is not broken.

De-duplicate the 'Core Capabilities' and 'Features' lists (both repeat INVEST validation and sprint planning) to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Lean body with no padding explaining agile basics and concrete commands inline, matching anchor 4; not 5 because 'Core Capabilities' and 'Features' redundantly repeat INVEST validation and sprint planning, plus a mildly marketing opening line.	4 / 5
Actionability	Provides concrete executable commands ('python scripts/user_story_generator.py' and the 'sprint [capacity]' variant), matching anchor 4; not 5 because it omits input format (where epics come from) and any example output.	4 / 5
Workflow Clarity	Only documents two invocation modes with no sequence or validation/verification checkpoints, matching anchor 3; the simple-skill exception does not lift this above 3 because batch story generation has no verification step.	3 / 5
Progressive Disclosure	Sections are organized but the body references scripts/user_story_generator.py while no scripts/ bundle exists, so the reference is broken; matches anchor 3 for structure present but navigation undermined.	3 / 5
	Total	14 / 20 Passed

Description

75%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, clearly naming the domain, several concrete capabilities, and an explicit 'Use for ...' trigger clause in third person. It stops short of the top anchor on each dimension due to minor coverage gaps and overlap between its 'what' and 'when' clauses.

Dimension	Reasoning	Score
Specificity	Lists four concrete actions (INVEST-compliant story generation, sprint planning, backlog management, velocity tracking), matching anchor 4; not 5 because 'stakeholder communication'/'agile ceremonies' are less concrete and acceptance-criteria creation is omitted.	4 / 5
Completeness	Has both an explicit 'what' (toolkit capabilities) and an explicit 'when' ('Use for ...'), matching anchor 4; not 5 because the when-clause largely repeats the what-clause (sprint planning appears in both) rather than adding distinct concrete triggers.	4 / 5
Trigger Term Quality	'story writing, sprint planning, stakeholder communication, agile ceremonies' are natural PO phrases, matching anchor 4; not 5 because common synonyms like 'user stories', 'backlog grooming/refinement', 'story points', and 'acceptance criteria' are missing.	4 / 5
Distinctiveness Conflict Risk	'Senior Product Owner' with INVEST-compliant story generation is a fairly distinct niche, matching anchor 4; not 5 because agile/scrum is a broad domain with overlap risk against generic scrum/agile skills.	4 / 5
	Total	16 / 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
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: Microck/ordinary-claude-skills
Path: skills_all/agile-product-owner/SKILL.md
Commit: 1056d29

Reviewed: 6 days 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.