cs-agile-product-owner

Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation. Use when preparing work for a development team — e.g., decomposing a large epic into INVEST-compliant stories with acceptance criteria, or refining a messy backlog ahead of sprint planning.

Quality

81%

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

Quality

Content

67%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.

A well-structured orchestration agent with concrete, executable workflow examples and clear external references. Its main weaknesses are verbosity (marketing prose, a Success Metrics section, repeated long paths) and review-based rather than automated validation loops.

Suggestions

Trim the Purpose section's value-prop prose and remove or relocate the Success Metrics block, which is informational rather than actionable, to improve conciseness.

Define the long relative script paths once (e.g. in a short variables/aliases table) and reuse short names in examples to cut repetition and fragility.

Add explicit automated feedback loops for the scripts (e.g. 'if generated stories fail INVEST checks, adjust epic.yaml and re-run') to lift workflow_clarity toward 5.

Dimension	Reasoning	Score
Conciseness	The body is efficient in the workflows but carries unnecessary prose (Purpose marketing lines like "bridges strategic product goals with sprint-level execution") and a non-actionable Success Metrics block, plus repeated full relative paths; this fits the mostly-efficient-but-could-be-tightened 3-anchor and not the trim 4-anchor.	3 / 5
Actionability	Provides copy-paste bash/YAML/CSV examples with concrete script invocations and flags (e.g. "python .../rice_prioritizer.py backlog.csv --capacity 20"), but the scripts' output formats and options are only described at a high level, leaving minor gaps versus the fully-executable 5-anchor.	4 / 5
Workflow Clarity	Four workflows are clearly sequenced with goals, steps, expected outputs, and review/validation checkpoints ("Validate INVEST compliance"), but validation is human-review-based rather than automated validate->fix->retry loops, so it sits at 4 rather than 5.	4 / 5
Progressive Disclosure	Good sectioning (Skill Integration table, Python Tools, Knowledge Bases, Templates, References) with clearly signaled one-level-deep external paths; no local bundle files exist, and substantial workflow content is inlined, which keeps it at 4 rather than the cleanly-split 5-anchor.	4 / 5
	Total	15 / 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.

A strong, third-person description that concisely states four concrete capabilities and provides an explicit "Use when" trigger with two realistic examples. Its only soft spot is modest overlap with sibling product-management agents on prioritization/backlog work.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation" — and reinforces them with concrete examples ("decomposing a large epic into INVEST-compliant stories with acceptance criteria"), giving comprehensive coverage rather than the 4-anchor's minor-gap profile.	5 / 5
Completeness	Explicitly answers both what (the four actions) and when via a "Use when preparing work for a development team — e.g., ..." clause with concrete trigger phrases, exactly matching the 5-anchor.	5 / 5
Trigger Term Quality	Uses natural PM terms a user would actually say ("epic breakdown", "sprint planning", "backlog refinement") plus synonyms ("decomposing a large epic"), matching the comprehensive-coverage anchor; file extensions are N/A for a process skill.	5 / 5
Distinctiveness Conflict Risk	The agile-PO framing (epics, sprints, backlog, INVEST) carves a clear niche, but it overlaps with closely related product-management skills (the very toolkit it orchestrates does RICE/PRDs), so it is mostly distinct with minor overlap rather than minimal conflict risk.	4 / 5
	Total	19 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing, 5 suspicious	Warning

	Total	14 / 16 Passed

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

Reviewed: ~4 hours 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.