Agent skill

Agile Product Owner

by alirezarezvani in alirezarezvani/claude-skills

Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

MITAuto-check passedProduct & Project Management

Install Agile Product Owner

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill agile-product-owner -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills agile-product-owner --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/product-team/agile-product-owner/skills/agile-product-owner .claude/skills/agile-product-owner && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agile-product-owner
GitHub stars
28k
Used in
3 other repos
Token cost
~3.2k tokens
SKILL.md length
1,012 words
Files
6 (incl. scripts, references, assets)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

  • Works in 8 steps: Identify the persona (who benefits from… → Define the action or capability needed → Articulate the benefit or value delivered → …
  • Turning requirements into user stories with testable acceptance criteria
  • SKILL.md covers Table of Contents, What Makes This Skill Different, User Story Generation Workflow and Acceptance Criteria Patterns, plus 6 more sections
  • Runs Python scripts from its folder; calls python

What it does

The story workflow runs from persona, action and benefit through Given-When-Then acceptance criteria and a Fibonacci estimate, then checks the result against INVEST criteria before the story joins the backlog. Acceptance criteria scale with story size so large items are not under-specified, and templates for features and improvements are provided.

Sprint capacity is calculated from velocity and an availability factor, epics are broken down with five split patterns, and the backlog is ranked with a weighted score of value 40%, impact 30%, risk 15% and effort 15%. Bundled files include user story and sprint planning templates, two reference guides and `scripts/user_story_generator.py`.

When your agent uses it

  • Turning requirements into user stories with testable acceptance criteria
  • Breaking a large epic into stories that fit a sprint
  • Planning a sprint based on team velocity and availability
  • Prioritizing a backlog with explicit weights

Example prompts

  • “Write user stories for exporting campaign reports to PDF, with Given-When-Then criteria.”
  • “Split the checkout redesign epic into sprint-sized stories.”
  • “Plan next sprint from our velocity and list which backlog items fit.”

Requirements

  • Python, for `scripts/user_story_generator.py`

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  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

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agile Product Owner loads about 3.2k tokens when it runs, and up to ~7.5k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 1,012 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,012 words, ~3,153 tokens.

Download SKILL.mdSave it as .claude/skills/agile-product-owner/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.
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 when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.
not_for
Kanban-only workflows, waterfall project planning, general task management, non-Scrum agile frameworks (SAFe, LeSS) without adaptation
triggers
write user story, create acceptance criteria, plan sprint, estimate story points, break down epic, prioritize backlog, sprint planning, backlog grooming…

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


What Makes This Skill Different

  • Capacity math that aligns with reality: sprint capacity is based on velocity × availability factor, not hope.
  • Acceptance criteria scaled by story size: minimum AC counts map to story points to avoid under-spec'ing large items.
  • Weighted prioritization that stays consistent: value 40%, impact 30%, risk 15%, effort 15% keeps tradeoffs explicit.
  • Systematic epic splitting techniques: five concrete split patterns prevent oversized stories.
  • INVEST validation baked into workflows: every story includes a validation step, not just guidance.

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
TypeTemplateExample
FeatureAs a [persona], I want to [action] so that [benefit]As a user, I want to filter search results so that I find items faster
ImprovementAs a [persona], I need [capability] to [goal]As a user, I need faster page loads to complete tasks without frustration
Bug FixAs a [persona], I expect [behavior] when [condition]As a user, I expect my cart to persist when I refresh the page
EnablerAs a developer, I need to [technical task] to enable [capability]As a developer, I need to implement caching to enable instant search
Persona Reference
PersonaTypical NeedsContext
End UserEfficiency, simplicity, reliabilityDaily feature usage
AdministratorControl, visibility, securitySystem management
Power UserAutomation, customization, shortcutsExpert workflows
New UserGuidance, learning, safetyOnboarding

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:

CategoryExample
Happy PathGiven valid input, When submitted, Then success message displayed
ValidationShould reject input when required field is empty
Error HandlingMust show user-friendly message when API fails
PerformanceShould complete operation within 2 seconds
AccessibilityMust be navigable via keyboard only
Minimum Criteria by Story Size
Story PointsMinimum AC Count
1-23-4 criteria
3-54-6 criteria
85-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
TechniqueWhen to UseExample
By workflow stepLinear process"Checkout" → "Add to cart" + "Enter payment" + "Confirm order"
By personaMultiple user types"Dashboard" → "Admin dashboard" + "User dashboard"
By data typeMultiple inputs"Import" → "Import CSV" + "Import Excel"
By operationCRUD functionality"Manage users" → "Create" + "Edit" + "Delete"
Happy path firstRisk 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
Show full SKILL.md (383 more words)Show less
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
ScenarioFactor
Full sprint, no PTO1.0
One team member out 50%0.9
Holiday during sprint0.8
Multiple members out0.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
PriorityDefinitionSprint Target
CriticalBlocking users, security, data lossImmediate
HighCore functionality, key user needsThis sprint
MediumImprovements, enhancementsNext 2-3 sprints
LowNice-to-have, minor improvementsBacklog
Prioritization Factors
FactorWeightQuestions
Business Value40%Revenue impact? User demand? Strategic alignment?
User Impact30%How many users? How frequently used?
Risk/Dependencies15%Technical risk? External dependencies?
Effort15%Size? Complexity? Uncertainty?
INVEST Criteria Validation

Before adding to sprint, validate each story:

CriterionQuestionPass If...
IndependentCan this be developed without other uncommitted stories?No blocking dependencies
NegotiableIs the implementation flexible?Multiple approaches possible
ValuableDoes this deliver user or business value?Clear benefit in "so that"
EstimableCan the team estimate this?Understood well enough to size
SmallCan this complete in one sprint?≤8 story points
TestableCan 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
bash
# 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
MetricFormulaTarget
VelocityPoints completed / sprintStable ±10%
Commitment ReliabilityCompleted / Committed>85%
Scope ChangePoints added or removed mid-sprint<10%
CarryoverPoints 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
  • Scrum Master (project-management/scrum-master/) — Velocity data and sprint ceremonies complement backlog management
  • Product Manager Toolkit (product-team/product-manager-toolkit/) — RICE prioritization feeds backlog ordering

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 5 other files (scripts, references, assets) in product-team/agile-product-owner/skills/agile-product-owner of alirezarezvani/claude-skills.

  • SKILL.md
  • assets/sprint_planning_template.md
  • assets/user_story_template.md
  • references/sprint-planning-guide.md
  • references/user-story-templates.md
  • scripts/user_story_generator.py

Open the folder on GitHubat commit 19392f7

Used in 3 other repositories

We found 4 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agile Product Owner next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agile Product Owner compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agile Product Owner this skillalirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Walking Skeleton Roadmap Scopingprime-radiant-inc/iterative-development181—~1.7kAutomated safety check: PassApache-2.0
Triagejoa23/linear-cli144—~699Automated safety check: PassMIT
Super Product Ownersyahiidkamil/Software-Engineer-AI-Agent-Atlas401—~7.9kAutomated safety check: PassNone
Product Managernagisanzenin/production-grade181—~3.7kAutomated safety check: PassNone
Bmad Prdaj-geddes/claude-code-bmad-skills488—~1.8kAutomated safety check: NotesCustom licence

Similar skills

  • Walking Skeleton Roadmap Scoping

    prime-radiant-inc/iterative-development

    Turns extracted requirements into a roadmap by choosing a walking skeleton iteration with its first journey scenario and ordering the remaining work into follow-on iterations.

    181 GitHub stars~1.7k tokensUpdated 4 mo ago
    Product & Project ManagementAuto-check passed
  • Triage

    joa23/linear-cli

    Triage and prioritize Linear backlog issues using the linear CLI.

    144 GitHub stars~699 tokensUpdated 27 days ago
    Product & Project ManagementAuto-check passed
  • Super Product Owner

    syahiidkamil/Software-Engineer-AI-Agent-Atlas

    Complete Product Owner / Product Manager capability — a wiki-style knowledge map of product practice in active software development: the role and its boundaries, strategy cascade (vision → OKRs →…

    401 GitHub stars~7.9k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check passed
  • Product Manager

    nagisanzenin/production-grade

    [production-grade internal] Turns product ideas and business goals into formal requirements — BRD, user stories, acceptance criteria, prioritization.

    181 GitHub stars~3.7k tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Bmad Prd

    aj-geddes/claude-code-bmad-skills

    PRD facilitator (John the PM). An agent skill from aj-geddes/claude-code-bmad-skills.

    488 GitHub stars~1.8k tokensUpdated 3 mo ago
    Product & Project ManagementAuto-check: notes
  • Oma Pm

    first-fluke/oh-my-agent

    Turn product requirements into scoped tasks with dependencies and acceptance criteria.

    1.3k GitHub stars~1.9k tokensUpdated yesterday
    Product & Project ManagementAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed
  • Customer Success Manager

    alirezarezvani/claude-skills

    Scores customer health, churn risk and expansion potential from a JSON export of account data, using three Python scripts that need no extra libraries.

    28k GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

Questions about Agile Product Owner

What does Agile Product Owner do?

Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score. The story workflow runs from persona, action and benefit through Given-When-Then acceptance criteria and a Fibonacci estimate, then checks the result against INVEST criteria before the story joins the backlog. Acceptance criteria scale with story size so large items are not under-specified, and templates for features and improvements are provided.

When should I use Agile Product Owner?

Agile Product Owner fits situations like: turning requirements into user stories with testable acceptance criteria; breaking a large epic into stories that fit a sprint; planning a sprint based on team velocity and availability; prioritizing a backlog with explicit weights.

How do I install Agile Product Owner in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill agile-product-owner -a claude-code`. Or copy the skill folder (product-team/agile-product-owner/skills/agile-product-owner in alirezarezvani/claude-skills) into .claude/skills/agile-product-owner in your project. Claude Code loads it when a task matches its description.

How do I install Agile Product Owner in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill agile-product-owner -a codex`. Or copy the skill folder (product-team/agile-product-owner/skills/agile-product-owner in alirezarezvani/claude-skills) into .agents/skills/agile-product-owner in your project. Codex loads it when a task matches its description.

Can I use Agile Product Owner in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill agile-product-owner -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agile-product-owner, .gemini/skills/agile-product-owner, .github/skills/agile-product-owner and .opencode/skills/agile-product-owner in your project.

What does Agile Product Owner need to run?

Going by SKILL.md and its folder, Agile Product Owner needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python, for `scripts/user_story_generator.py`.

Does Agile Product Owner access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agile Product Owner safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Agile Product Owner use?

Agile Product Owner is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agile Product Owner use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.

What are the alternatives to Agile Product Owner?

Skills that share tags, products or a category with Agile Product Owner: Walking Skeleton Roadmap Scoping (prime-radiant-inc/iterative-development, 181 stars), Triage (joa23/linear-cli, 144 stars), Super Product Owner (syahiidkamil/Software-Engineer-AI-Agent-Atlas, 401 stars) and Product Manager (nagisanzenin/production-grade, 181 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agile Product Owner?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.