SkillAgentSearch skills...

agile-product-owner

Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking.

Install / Use

npx skills add LeoYeAI/openclaw-master-skills --skill agile-product-owner

Installs into whichever agent you are using.

About this skill
๐Ÿ“„

SKILL.md

Installable skill definition

Quality Score

88/100

Supported Platforms

Universal

Tags

Our assessment of agile-product-owner

agile-product-owner scores 88/100 on our quality scale, 584th of 1,153 Content & Media skills we index.

Its SKILL.md is 11 KB long, well organised into 33 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

With 2,149 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
14/20
Freshness
11/15

Maintenance, license and trust

  • The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.
  • Our last check on 2026-11-01 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 98/100, with no cautions. These come from repository metadata, not a code audit โ€” read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-30. It catches known dangerous patterns, not every risk โ€” read a skill before letting an agent act on it.

agile-product-owner compared with similar skills

All 4 of these similar skills score higher than agile-product-owner; compare them before choosing.

SkillScoreStarsUpdatedFormat
agile-product-owner (this skill)by LeoYeAI882.1k4mo agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install agile-product-owner?
Run npx skills add LeoYeAI/openclaw-master-skills --skill agile-product-owner. The install tabs above show the steps for each supported agent.
Which AI agents does agile-product-owner work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is agile-product-owner safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 98/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is agile-product-owner still maintained?
The repository was last updated about 4 months ago. That is recent enough to be usable, but agent tooling moves fast, so check the instructions against your agent's current version.

name: "agile-product-owner" description: 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. triggers:

  • write user story
  • create acceptance criteria
  • plan sprint
  • estimate story points
  • break down epic
  • prioritize backlog
  • sprint planning
  • INVEST criteria
  • Given When Then
  • user story template
  • sprint capacity
  • velocity tracking

Agile Product Owner

Backlog management and sprint execution toolkit for product owners, including user story generation, acceptance criteria patterns, sprint planning, and velocity tracking.


Table of Contents


User Story Generation Workflow

Create INVEST-compliant user stories from requirements:

  1. Identify the persona (who benefits from this feature)
  2. Define the action or capability needed
  3. Articulate the benefit or value delivered
  4. Write acceptance criteria using Given-When-Then
  5. Estimate story points using Fibonacci scale
  6. Validate against INVEST criteria
  7. Add to backlog with priority
  8. Validation: Story passes all INVEST criteria; acceptance criteria are testable

User Story Template

As a [persona],
I want to [action/capability],
So that [benefit/value].

Example:

As a marketing manager,
I want to export campaign reports to PDF,
So that I can share results with stakeholders who don't have system access.

Story Types

| Type | Template | Example | |------|----------|---------| | Feature | As a [persona], I want to [action] so that [benefit] | As a user, I want to filter search results so that I find items faster | | Improvement | As a [persona], I need [capability] to [goal] | As a user, I need faster page loads to complete tasks without frustration | | Bug Fix | As a [persona], I expect [behavior] when [condition] | As a user, I expect my cart to persist when I refresh the page | | Enabler | As a developer, I need to [technical task] to enable [capability] | As a developer, I need to implement caching to enable instant search |

Persona Reference

| Persona | Typical Needs | Context | |---------|--------------|---------| | End User | Efficiency, simplicity, reliability | Daily feature usage | | Administrator | Control, visibility, security | System management | | Power User | Automation, customization, shortcuts | Expert workflows | | New User | Guidance, learning, safety | Onboarding |


Acceptance Criteria Patterns

Write testable acceptance criteria using Given-When-Then format.

Given-When-Then Template

Given [precondition/context],
When [action/trigger],
Then [expected outcome].

Examples:

Given the user is logged in with valid credentials,
When they click the "Export" button,
Then a PDF download starts within 2 seconds.

Given the user has entered an invalid email format,
When they submit the registration form,
Then an inline error message displays "Please enter a valid email address."

Given the shopping cart contains items,
When the user refreshes the browser,
Then the cart contents remain unchanged.

Acceptance Criteria Checklist

Each story should include criteria for:

| Category | Example | |----------|---------| | Happy Path | Given valid input, When submitted, Then success message displayed | | Validation | Should reject input when required field is empty | | Error Handling | Must show user-friendly message when API fails | | Performance | Should complete operation within 2 seconds | | Accessibility | Must be navigable via keyboard only |

Minimum Criteria by Story Size

| Story Points | Minimum AC Count | |--------------|------------------| | 1-2 | 3-4 criteria | | 3-5 | 4-6 criteria | | 8 | 5-8 criteria | | 13+ | Split the story |

See references/user-story-templates.md for complete template library.


Epic Breakdown Workflow

Break epics into deliverable sprint-sized stories:

  1. Define epic scope and success criteria
  2. Identify all personas affected by the epic
  3. List all capabilities needed for each persona
  4. Group capabilities into logical stories
  5. Validate each story is โ‰ค8 points
  6. Identify dependencies between stories
  7. Sequence stories for incremental delivery
  8. Validation: Each story delivers standalone value; total stories cover epic scope

Splitting Techniques

| Technique | When to Use | Example | |-----------|-------------|---------| | By workflow step | Linear process | "Checkout" โ†’ "Add to cart" + "Enter payment" + "Confirm order" | | By persona | Multiple user types | "Dashboard" โ†’ "Admin dashboard" + "User dashboard" | | By data type | Multiple inputs | "Import" โ†’ "Import CSV" + "Import Excel" | | By operation | CRUD functionality | "Manage users" โ†’ "Create" + "Edit" + "Delete" | | Happy path first | Risk reduction | "Feature" โ†’ "Basic flow" + "Error handling" + "Edge cases" |

Epic Example

Epic: User Dashboard

Breakdown:

Epic: User Dashboard (34 points total)
โ”œโ”€โ”€ US-001: View key metrics (5 pts) - End User
โ”œโ”€โ”€ US-002: Customize layout (5 pts) - Power User
โ”œโ”€โ”€ US-003: Export data to CSV (3 pts) - End User
โ”œโ”€โ”€ US-004: Share with team (5 pts) - End User
โ”œโ”€โ”€ US-005: Set up alerts (5 pts) - Power User
โ”œโ”€โ”€ US-006: Filter by date range (3 pts) - End User
โ”œโ”€โ”€ US-007: Admin overview (5 pts) - Admin
โ””โ”€โ”€ US-008: Enable caching (3 pts) - Enabler

Sprint Planning Workflow

Plan sprint capacity and select stories:

  1. Calculate team capacity (velocity ร— availability)
  2. Review sprint goal with stakeholders
  3. Select stories from prioritized backlog
  4. Fill to 80-85% of capacity (committed)
  5. Add stretch goals (10-15% additional)
  6. Identify dependencies and risks
  7. Break complex stories into tasks
  8. Validation: Committed points โ‰ค85% capacity; all stories have acceptance criteria

Capacity Calculation

Sprint Capacity = Average Velocity ร— Availability Factor

Example:
Average Velocity: 30 points
Team availability: 90% (one member partially out)
Adjusted Capacity: 27 points

Committed: 23 points (85% of 27)
Stretch: 4 points (15% of 27)

Availability Factors

| Scenario | Factor | |----------|--------| | Full sprint, no PTO | 1.0 | | One team member out 50% | 0.9 | | Holiday during sprint | 0.8 | | Multiple members out | 0.7 |

Sprint Loading Template

Sprint Capacity: 27 points
Sprint Goal: [Clear, measurable objective]

COMMITTED (23 points):
[H] US-001: User dashboard (5 pts)
[H] US-002: Export feature (3 pts)
[H] US-003: Search filter (5 pts)
[M] US-004: Settings page (5 pts)
[M] US-005: Help tooltips (3 pts)
[L] US-006: Theme options (2 pts)

STRETCH (4 points):
[L] US-007: Sort options (2 pts)
[L] US-008: Print view (2 pts)

See references/sprint-planning-guide.md for complete planning procedures.


Backlog Prioritization

Prioritize backlog using value and effort assessment.

Priority Levels

| Priority | Definition | Sprint Target | |----------|------------|---------------| | Critical | Blocking users, security, data loss | Immediate | | High | Core functionality, key user needs | This sprint | | Medium | Improvements, enhancements | Next 2-3 sprints | | Low | Nice-to-have, minor improvements | Backlog |

Prioritization Factors

| Factor | Weight | Questions | |--------|--------|-----------| | Business Value | 40% | Revenue impact? User demand? Strategic alignment? | | User Impact | 30% | How many users? How frequently used? | | Risk/Dependencies | 15% | Technical risk? External dependencies? | | Effort | 15% | Size? Complexity? Uncertainty? |

INVEST Criteria Validation

Before adding to sprint, validate each story:

| Criterion | Question | Pass If... | |-----------|----------|------------| | Independent | Can this be developed without other uncommitted stories? | No blocking dependencies | | Negotiable | Is the implementation flexible? | Multiple approaches possible | | Valuable | Does this deliver user or business value? | Clear benefit in "so that" | | Estimable | Can the team estimate this? | Understood well enough to size | | Small | Can this complete in one sprint? | โ‰ค8 story points | | Testable | Can we verify this is done? | Clear acceptance criteria |


Reference Documentation

User Story Templates

references/user-story-templates.md contains:

  • Standard story formats by type (feature, improvement, bug fix, enabler)
  • Acceptance criteria patterns (Given-When-Then, Should/Must/Can)
  • INVEST criteria validation checklist
  • Story point estimation guide (Fibonacci scale)
  • Common story antipatterns and fixes
  • Story splitting techniques

Sprint Planning Guide

references/sprint-planning-guide.md contains:

  • Sprint planning meeting agenda
  • Capacity calculation formulas
  • Backlog prioritization framework (WSJF)
  • Sprint ceremony guides (standup, review, retro)
  • Velocity tracking and burndown patterns
  • Definition of Done checklist
  • Sprint metrics and targets

Tools

User Story Generator

# Generate stories from sample epic
python scripts/user_story_generator.py

# Plan sprint with capacity
python scripts/user_story_generator.py sprint 30

Generates:

  • INVEST-compliant user stories
  • Given-When-Then acceptance criteria
  • Story point estimates (Fibonacci scale)
  • Priority assignments
  • Sprint loading with committed and stretch items

Sample Output

USER STORY: USR-001
========================================
Title: View Key Metrics
Type: story
Priority: HIGH
Points: 5

Story:
As a End User, I want to view key metrics and KPIs
so that I can save time and work more efficiently

Acceptance Criteria:
  1. Given user has access, When they view key metrics, Then the result is displayed
  2. Should validate input before processing
  3. Must show clear error message when action fails
  4. Should complete within 2 seconds
  5. Must be accessible via keyboard navigation

INVEST Checklist:
  โœ“ Independent
  โœ“ Negotiable
  โœ“ Valuable
  โœ“ Estimable
  โœ“ Small
  โœ“ Testable

Sprint Metrics

Track sprint health and team performance.

Key Metrics

| Metric | Formula | Target | |--------|---------|--------| | Velocity | Points completed / sprint | Stable ยฑ10% | | Commitment Reliability | Completed / Committed | >85% | | Scope Change | Points added or removed mid-sprint | <10% | | Carryover | Points not completed | <15% |

Velocity Tracking

Sprint 1: 25 points
Sprint 2: 28 points
Sprint 3: 30 points
Sprint 4: 32 points
Sprint 5: 29 points
------------------------
Average Velocity: 28.8 points
Trend: Stable

Planning: Commit to 24-26 points

Definition of Done

Story is complete when:

  • [ ] Code complete and peer reviewed
  • [ ] Unit tests written and passing
  • [ ] Acceptance criteria verified
  • [ ] Documentation updated
  • [ ] Deployed to staging environment
  • [ ] Product Owner accepted
  • [ ] No critical bugs remaining

Related Skills

View on GitHub
GitHub Stars2.1k
CategoryContent
Updated3mo ago
Forks325

Languages

Python

Trust signals

98/100

From repository metadata: license, adoption, age and documentation. Not a code audit โ€” see the Safety scan above for what the skill file itself contains.

1 info
agile-product-owner โ€” Universal Skill: Install & Safety Check | SkillAgent