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.mdUser story writing & INVEST compliance
Standard story format
90%
100%
Multiple personas
100%
100%
GWT acceptance criteria
0%
100%
AC category coverage
100%
100%
Fibonacci estimates
100%
100%
Minimum AC count
100%
100%
Stories ≤8 points
37%
100%
INVEST checklist present
10%
100%
No compound stories
62%
75%
Benefit clause present
100%
100%
Antipattern review
100%
100%
Epic decomposition into sprint-sized stories
All stories ≤8 points
100%
100%
Fibonacci-only estimates
100%
100%
Standalone value per story
100%
100%
Scope coverage validation
100%
100%
Splitting technique applied
100%
100%
Multiple personas identified
100%
100%
Dependencies mapped
100%
100%
Incremental delivery sequence
100%
100%
Technical enabler included
100%
100%
Priority assigned
100%
100%
Epic success criteria
100%
100%
Sprint capacity planning & story selection
Average velocity calculated
100%
100%
Availability factor applied
100%
100%
Adjusted capacity shown
100%
100%
Committed at 80-85%
0%
100%
Stretch goals present
40%
70%
Committed vs stretch separated
100%
100%
Dependency respected
100%
100%
Percentage utilization stated
100%
100%
Validation statement present
100%
100%
Capacity formula shown
100%
100%
Priority respected in selection
100%
100%
Backlog prioritization with WSJF
WSJF formula applied
100%
100%
WSJF Fibonacci scale
100%
100%
Cost of Delay components
100%
100%
Items ranked by WSJF
100%
100%
Explicit WSJF score per item
100%
100%
Priority levels assigned
100%
100%
Backlog sections present
100%
100%
Items distributed across sections
100%
100%
Business value weight
0%
0%
User impact weight
0%
0%
Sprint metrics and velocity analysis
Velocity formula correct
100%
100%
Velocity stability target
0%
100%
Commitment Reliability threshold
66%
100%
Scope Change threshold
100%
100%
Carryover threshold
25%
100%
Bug Ratio threshold
62%
37%
Velocity trend identified
100%
100%
Planning recommendation
100%
100%
Definition of Done checklist
100%
100%
Burndown pattern interpretation
100%
100%
Sprint ceremony structure and backlog readiness
Sprint planning duration
100%
100%
Daily standup duration
100%
100%
Standup 3-question format
100%
100%
Refinement scheduled mid-sprint
100%
100%
Refinement duration
100%
100%
Sprint review duration
100%
100%
Retrospective duration
0%
60%
Named retrospective format
100%
100%
Retro action item cap
100%
100%
Backlog readiness criteria
100%
100%
a96cc20
Table of Contents
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.