跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

agile-product-owner

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.

alirezarezvani · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add alirezarezvani/claude-skills --skill agile-product-owner

技能说明


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
  • sprint retrospective
  • definition of done
  • 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


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
阅读完整来源 ↗