agile-product-owner by alirezarezvani/claude-skills
npx skills add https://github.com/alirezarezvani/claude-skills --skill agile-product-owner产品负责人的待办事项管理和冲刺执行工具包,包括用户故事生成、验收标准模式、冲刺规划和速率跟踪。
从需求创建符合 INVEST 原则的用户故事:
As a [persona],
I want to [action/capability],
So that [benefit/value].
示例:
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.
| 类型 |
|---|
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 模板 |
|---|
| 示例 |
|---|
| 功能 | 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 |
| 改进 | As a [persona], I need [capability] to [goal] | As a user, I need faster page loads to complete tasks without frustration |
| 缺陷修复 | As a [persona], I expect [behavior] when [condition] | As a user, I expect my cart to persist when I refresh the page |
| 使能项 | As a developer, I need to [technical task] to enable [capability] | As a developer, I need to implement caching to enable instant search |
| 角色 | 典型需求 | 上下文 |
|---|---|---|
| 最终用户 | 效率、简洁性、可靠性 | 日常功能使用 |
| 管理员 | 控制、可见性、安全性 | 系统管理 |
| 高级用户 | 自动化、自定义、快捷方式 | 专家工作流 |
| 新用户 | 引导、学习、安全性 | 入门 |
使用 Given-When-Then 格式编写可测试的验收标准。
Given [precondition/context],
When [action/trigger],
Then [expected outcome].
示例:
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.
每个故事应包含以下类别的标准:
| 类别 | 示例 |
|---|---|
| 理想路径 | Given valid input, When submitted, Then success message displayed |
| 验证 | Should reject input when required field is empty |
| 错误处理 | Must show user-friendly message when API fails |
| 性能 | Should complete operation within 2 seconds |
| 可访问性 | Must be navigable via keyboard only |
| 故事点 | 最小验收标准数量 |
|---|---|
| 1-2 | 3-4 条标准 |
| 3-5 | 4-6 条标准 |
| 8 | 5-8 条标准 |
| 13+ | 拆分故事 |
完整模板库请参阅 references/user-story-templates.md。
将史诗分解为可交付的冲刺规模的故事:
| 技术 | 使用时机 | 示例 |
|---|---|---|
| 按工作流步骤 | 线性流程 | "Checkout" → "Add to cart" + "Enter payment" + "Confirm order" |
| 按角色 | 多种用户类型 | "Dashboard" → "Admin dashboard" + "User dashboard" |
| 按数据类型 | 多种输入 | "Import" → "Import CSV" + "Import Excel" |
| 按操作 | CRUD 功能 | "Manage users" → "Create" + "Edit" + "Delete" |
| 理想路径优先 | 风险降低 | "Feature" → "Basic flow" + "Error handling" + "Edge cases" |
史诗: 用户仪表板
分解:
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 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)
| 场景 | 因子 |
|---|---|
| 完整冲刺,无带薪休假 | 1.0 |
| 一名团队成员缺席 50% | 0.9 |
| 冲刺期间有节假日 | 0.8 |
| 多名成员缺席 | 0.7 |
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)
完整规划流程请参阅 references/sprint-planning-guide.md。
使用价值和努力评估对待办事项进行优先级排序。
| 优先级 | 定义 | 冲刺目标 |
|---|---|---|
| 关键 | 阻塞用户、安全性、数据丢失 | 立即 |
| 高 | 核心功能、关键用户需求 | 本次冲刺 |
| 中 | 改进、增强 | 未来 2-3 次冲刺 |
| 低 | 锦上添花、微小改进 | 待办事项列表 |
| 因子 | 权重 | 问题 |
|---|---|---|
| 业务价值 | 40% | 收入影响?用户需求?战略一致性? |
| 用户影响 | 30% | 多少用户?使用频率? |
| 风险/依赖关系 | 15% | 技术风险?外部依赖? |
| 工作量 | 15% | 规模?复杂度?不确定性? |
在添加到冲刺之前,验证每个故事:
| 原则 | 问题 | 通过条件 |
|---|---|---|
| I ndependent(独立的) | 能否在没有其他未承诺故事的情况下开发此故事? | 无阻塞依赖关系 |
| N egotiable(可协商的) | 实现方式是否灵活? | 多种方法可行 |
| V aluable(有价值的) | 是否交付用户或业务价值? | "so that" 部分有明确收益 |
| E stimable(可估算的) | 团队能否估算此故事? | 足够理解以确定规模 |
| S mall(小的) | 能否在一个冲刺内完成? | ≤8 故事点 |
| T estable(可测试的) | 能否验证已完成? | 明确的验收标准 |
references/user-story-templates.md 包含:
references/sprint-planning-guide.md 包含:
# Generate stories from sample epic
python scripts/user_story_generator.py
# Plan sprint with capacity
python scripts/user_story_generator.py sprint 30
生成:
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
跟踪冲刺健康状况和团队绩效。
| 指标 | 公式 | 目标 |
|---|---|---|
| 速率 | 已完成点数 / 冲刺 | 稳定 ±10% |
| 承诺可靠性 | 已完成 / 已承诺 | >85% |
| 范围变更 | 冲刺中期添加或移除的点数 | <10% |
| 遗留项 | 未完成的点数 | <15% |
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
故事在以下情况下完成:
每周安装数
222
仓库
GitHub 星标数
2.8K
首次出现
Jan 20, 2026
安全审计
安装于
claude-code178
gemini-cli172
opencode172
codex160
github-copilot147
cursor147
Backlog management and sprint execution toolkit for product owners, including user story generation, acceptance criteria patterns, sprint planning, and velocity tracking.
Create INVEST-compliant user stories from requirements:
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.
| 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 | 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 |
Write testable acceptance criteria using Given-When-Then format.
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.
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 |
| 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.
Break epics into deliverable sprint-sized stories:
| 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: 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
Plan sprint capacity and select stories:
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)
| 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 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.
Prioritize backlog using value and effort assessment.
| 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 |
| 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? |
Before adding to sprint, validate each story:
| Criterion | Question | Pass If... |
|---|---|---|
| I ndependent | Can this be developed without other uncommitted stories? | No blocking dependencies |
| N egotiable | Is the implementation flexible? | Multiple approaches possible |
| V aluable | Does this deliver user or business value? | Clear benefit in "so that" |
| E stimable | Can the team estimate this? | Understood well enough to size |
| S mall | Can this complete in one sprint? | ≤8 story points |
| T estable | Can we verify this is done? | Clear acceptance criteria |
references/user-story-templates.md contains:
references/sprint-planning-guide.md contains:
# Generate stories from sample epic
python scripts/user_story_generator.py
# Plan sprint with capacity
python scripts/user_story_generator.py sprint 30
Generates:
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
Track sprint health and team performance.
| 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% |
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
Story is complete when:
Weekly Installs
222
Repository
GitHub Stars
2.8K
First Seen
Jan 20, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
claude-code178
gemini-cli172
opencode172
codex160
github-copilot147
cursor147
飞书日程待办摘要工作流:AI自动生成每日/每周开工报告,提升个人生产力
24,200 周安装