[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71M934W1T2C5HFMGJ3EECDK":3,"skill-same:01M71M934W1T2C5HFMGJ3EECDK":101},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":58,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M71M934W1T2C5HFMGJ3EECDK","agile-product-owner",null,"Use when writing INVEST user stories and Given-When-Then acceptance criteria, splitting epics, estimating points and planning sprints from velocity. Hands-on backlog toolkit; for deciding sprint scope as an org role see sprint-prioritizer.","monoes\u002Fmonomind","monoes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F276744696?v=4","01M71KWF37AJ2NJBP3KWBVSDGT","01M71KWF4CSF8ADH0M6HA09VD2",23,"MIT","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,5,34,35,36,37,38,39,40,41,42],"agile","agile product owner","product","for","planning","hands-on","as","sprints","user stories","org","velocity","documentation","team","when","acceptance","writing","scope","sprint","claude-skills","2026-11-10 10:56:23",false,"---\nname: agile-product-owner\ndescription: \"Use when writing INVEST user stories and Given-When-Then acceptance criteria, splitting epics, estimating points and planning sprints from velocity. Hands-on backlog toolkit; for deciding sprint scope as an org role see sprint-prioritizer.\"\ntags: [\"product\",\"planning\",\"documentation\"]\ntools: []\nlicense: MIT\nsource: https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills\nsource_path: \"product-team\u002Fagile-product-owner\u002Fskills\u002Fagile-product-owner\"\nsource_commit: 19392f7a08264ed00486a251f5b2098321771f94\n---\n# Agile Product Owner\n\nBacklog management and sprint execution toolkit for product owners, including user story generation, acceptance criteria patterns, sprint planning, and velocity tracking.\n\n---\n\n## Table of Contents\n\n- [What Makes This Skill Different](#what-makes-this-skill-different)\n- [User Story Generation Workflow](#user-story-generation-workflow)\n- [Acceptance Criteria Patterns](#acceptance-criteria-patterns)\n- [Epic Breakdown Workflow](#epic-breakdown-workflow)\n- [Sprint Planning Workflow](#sprint-planning-workflow)\n- [Backlog Prioritization](#backlog-prioritization)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## What Makes This Skill Different\n\n- **Capacity math that aligns with reality:** sprint capacity is based on velocity × availability factor, not hope.\n- **Acceptance criteria scaled by story size:** minimum AC counts map to story points to avoid under-spec'ing large items.\n- **Weighted prioritization that stays consistent:** value 40%, impact 30%, risk 15%, effort 15% keeps tradeoffs explicit.\n- **Systematic epic splitting techniques:** five concrete split patterns prevent oversized stories.\n- **INVEST validation baked into workflows:** every story includes a validation step, not just guidance.\n\n## User Story Generation Workflow\n\nCreate INVEST-compliant user stories from requirements:\n\n1. Identify the persona (who benefits from this feature)\n2. Define the action or capability needed\n3. Articulate the benefit or value delivered\n4. Write acceptance criteria using Given-When-Then\n5. Estimate story points using Fibonacci scale\n6. Validate against INVEST criteria\n7. Add to backlog with priority\n8. **Validation:** Story passes all INVEST criteria; acceptance criteria are testable\n\n### User Story Template\n\n```\nAs a [persona],\nI want to [action\u002Fcapability],\nSo that [benefit\u002Fvalue].\n```\n\n**Example:**\n```\nAs a marketing manager,\nI want to export campaign reports to PDF,\nSo that I can share results with stakeholders who don't have system access.\n```\n\n### Story Types\n\n| Type | Template | Example |\n|------|----------|---------|\n| 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 |\n| Improvement | As a [persona], I need [capability] to [goal] | As a user, I need faster page loads to complete tasks without frustration |\n| Bug Fix | As a [persona], I expect [behavior] when [condition] | As a user, I expect my cart to persist when I refresh the page |\n| Enabler | As a developer, I need to [technical task] to enable [capability] | As a developer, I need to implement caching to enable instant search |\n\n### Persona Reference\n\n| Persona | Typical Needs | Context |\n|---------|--------------|---------|\n| End User | Efficiency, simplicity, reliability | Daily feature usage |\n| Administrator | Control, visibility, security | System management |\n| Power User | Automation, customization, shortcuts | Expert workflows |\n| New User | Guidance, learning, safety | Onboarding |\n\n---\n\n## Acceptance Criteria Patterns\n\nWrite testable acceptance criteria using Given-When-Then format.\n\n### Given-When-Then Template\n\n```\nGiven [precondition\u002Fcontext],\nWhen [action\u002Ftrigger],\nThen [expected outcome].\n```\n\n**Examples:**\n```\nGiven the user is logged in with valid credentials,\nWhen they click the \"Export\" button,\nThen a PDF download starts within 2 seconds.\n\nGiven the user has entered an invalid email format,\nWhen they submit the registration form,\nThen an inline error message displays \"Please enter a valid email address.\"\n\nGiven the shopping cart contains items,\nWhen the user refreshes the browser,\nThen the cart contents remain unchanged.\n```\n\n### Acceptance Criteria Checklist\n\nEach story should include criteria for:\n\n| Category | Example |\n|----------|---------|\n| Happy Path | Given valid input, When submitted, Then success message displayed |\n| Validation | Should reject input when required field is empty |\n| Error Handling | Must show user-friendly message when API fails |\n| Performance | Should complete operation within 2 seconds |\n| Accessibility | Must be navigable via keyboard only |\n\n### Minimum Criteria by Story Size\n\n| Story Points | Minimum AC Count |\n|--------------|------------------|\n| 1-2 | 3-4 criteria |\n| 3-5 | 4-6 criteria |\n| 8 | 5-8 criteria |\n| 13+ | Split the story |\n\nSee `references\u002Fuser-story-templates.md` for complete template library.\n\n---\n\n## Epic Breakdown Workflow\n\nBreak epics into deliverable sprint-sized stories:\n\n1. Define epic scope and success criteria\n2. Identify all personas affected by the epic\n3. List all capabilities needed for each persona\n4. Group capabilities into logical stories\n5. Validate each story is ≤8 points\n6. Identify dependencies between stories\n7. Sequence stories for incremental delivery\n8. **Validation:** Each story delivers standalone value; total stories cover epic scope\n\n### Splitting Techniques\n\n| Technique | When to Use | Example |\n|-----------|-------------|---------|\n| By workflow step | Linear process | \"Checkout\" → \"Add to cart\" + \"Enter payment\" + \"Confirm order\" |\n| By persona | Multiple user types | \"Dashboard\" → \"Admin dashboard\" + \"User dashboard\" |\n| By data type | Multiple inputs | \"Import\" → \"Import CSV\" + \"Import Excel\" |\n| By operation | CRUD functionality | \"Manage users\" → \"Create\" + \"Edit\" + \"Delete\" |\n| Happy path first | Risk reduction | \"Feature\" → \"Basic flow\" + \"Error handling\" + \"Edge cases\" |\n\n### Epic Example\n\n**Epic:** User Dashboard\n\n**Breakdown:**\n```\nEpic: User Dashboard (34 points total)\n├── US-001: View key metrics (5 pts) - End User\n├── US-002: Customize layout (5 pts) - Power User\n├── US-003: Export data to CSV (3 pts) - End User\n├── US-004: Share with team (5 pts) - End User\n├── US-005: Set up alerts (5 pts) - Power User\n├── US-006: Filter by date range (3 pts) - End User\n├── US-007: Admin overview (5 pts) - Admin\n└── US-008: Enable caching (3 pts) - Enabler\n```\n\n---\n\n## Sprint Planning Workflow\n\nPlan sprint capacity and select stories:\n\n1. Calculate team capacity (velocity × availability)\n2. Review sprint goal with stakeholders\n3. Select stories from prioritized backlog\n4. Fill to 80-85% of capacity (committed)\n5. Add stretch goals (10-15% additional)\n6. Identify dependencies and risks\n7. Break complex stories into tasks\n8. **Validation:** Committed points ≤85% capacity; all stories have acceptance criteria\n\n### Capacity Calculation\n\n```\nSprint Capacity = Average Velocity × Availability Factor\n\nExample:\nAverage Velocity: 30 points\nTeam availability: 90% (one member partially out)\nAdjusted Capacity: 27 points\n\nCommitted: 23 points (85% of 27)\nStretch: 4 points (15% of 27)\n```\n\n### Availability Factors\n\n| Scenario | Factor |\n|----------|--------|\n| Full sprint, no PTO | 1.0 |\n| One team member out 50% | 0.9 |\n| Holiday during sprint | 0.8 |\n| Multiple members out | 0.7 |\n\n### Sprint Loading Template\n\n```\nSprint Capacity: 27 points\nSprint Goal: [Clear, measurable objective]\n\nCOMMITTED (23 points):\n[H] US-001: User dashboard (5 pts)\n[H] US-002: Export feature (3 pts)\n[H] US-003: Search filter (5 pts)\n[M] US-004: Settings page (5 pts)\n[M] US-005: Help tooltips (3 pts)\n[L] US-006: Theme options (2 pts)\n\nSTRETCH (4 points):\n[L] US-007: Sort options (2 pts)\n[L] US-008: Print view (2 pts)\n```\n\nSee `references\u002Fsprint-planning-guide.md` for complete planning procedures.\n\n---\n\n## Backlog Prioritization\n\nPrioritize backlog using value and effort assessment.\n\n### Priority Levels\n\n| Priority | Definition | Sprint Target |\n|----------|------------|---------------|\n| Critical | Blocking users, security, data loss | Immediate |\n| High | Core functionality, key user needs | This sprint |\n| Medium | Improvements, enhancements | Next 2-3 sprints |\n| Low | Nice-to-have, minor improvements | Backlog |\n\n### Prioritization Factors\n\n| Factor | Weight | Questions |\n|--------|--------|-----------|\n| Business Value | 40% | Revenue impact? User demand? Strategic alignment? |\n| User Impact | 30% | How many users? How frequently used? |\n| Risk\u002FDependencies | 15% | Technical risk? External dependencies? |\n| Effort | 15% | Size? Complexity? Uncertainty? |\n\n### INVEST Criteria Validation\n\nBefore adding to sprint, validate each story:\n\n| Criterion | Question | Pass If... |\n|-----------|----------|------------|\n| **I**ndependent | Can this be developed without other uncommitted stories? | No blocking dependencies |\n| **N**egotiable | Is the implementation flexible? | Multiple approaches possible |\n| **V**aluable | Does this deliver user or business value? | Clear benefit in \"so that\" |\n| **E**stimable | Can the team estimate this? | Understood well enough to size |\n| **S**mall | Can this complete in one sprint? | ≤8 story points |\n| **T**estable | Can we verify this is done? | Clear acceptance criteria |\n\n---\n\n## Reference Documentation\n\n### User Story Templates\n\n`references\u002Fuser-story-templates.md` contains:\n\n- Standard story formats by type (feature, improvement, bug fix, enabler)\n- Acceptance criteria patterns (Given-When-Then, Should\u002FMust\u002FCan)\n- INVEST criteria validation checklist\n- Story point estimation guide (Fibonacci scale)\n- Common story antipatterns and fixes\n- Story splitting techniques\n\n### Sprint Planning Guide\n\n`references\u002Fsprint-planning-guide.md` contains:\n\n- Sprint planning meeting agenda\n- Capacity calculation formulas\n- Backlog prioritization framework (WSJF)\n- Sprint ceremony guides (standup, review, retro)\n- Velocity tracking and burndown patterns\n- Definition of Done checklist\n- Sprint metrics and targets\n\n---\n\n## Tools\n\n### User Story Generator\n\n```bash\n# Generate stories from sample epic\npython scripts\u002Fuser_story_generator.py\n\n# Plan sprint with capacity\npython scripts\u002Fuser_story_generator.py sprint 30\n```\n\nGenerates:\n- INVEST-compliant user stories\n- Given-When-Then acceptance criteria\n- Story point estimates (Fibonacci scale)\n- Priority assignments\n- Sprint loading with committed and stretch items\n\n### Sample Output\n\n```\nUSER STORY: USR-001\n========================================\nTitle: View Key Metrics\nType: story\nPriority: HIGH\nPoints: 5\n\nStory:\nAs a End User, I want to view key metrics and KPIs\nso that I can save time and work more efficiently\n\nAcceptance Criteria:\n  1. Given user has access, When they view key metrics, Then the result is displayed\n  2. Should validate input before processing\n  3. Must show clear error message when action fails\n  4. Should complete within 2 seconds\n  5. Must be accessible via keyboard navigation\n\nINVEST Checklist:\n  ✓ Independent\n  ✓ Negotiable\n  ✓ Valuable\n  ✓ Estimable\n  ✓ Small\n  ✓ Testable\n```\n\n---\n\n## Sprint Metrics\n\nTrack sprint health and team performance.\n\n### Key Metrics\n\n| Metric | Formula | Target |\n|--------|---------|--------|\n| Velocity | Points completed \u002F sprint | Stable ±10% |\n| Commitment Reliability | Completed \u002F Committed | >85% |\n| Scope Change | Points added or removed mid-sprint | \u003C10% |\n| Carryover | Points not completed | \u003C15% |\n\n### Velocity Tracking\n\n```\nSprint 1: 25 points\nSprint 2: 28 points\nSprint 3: 30 points\nSprint 4: 32 points\nSprint 5: 29 points\n------------------------\nAverage Velocity: 28.8 points\nTrend: Stable\n\nPlanning: Commit to 24-26 points\n```\n\n### Definition of Done\n\nStory is complete when:\n\n- [ ] Code complete and peer reviewed\n- [ ] Unit tests written and passing\n- [ ] Acceptance criteria verified\n- [ ] Documentation updated\n- [ ] Deployed to staging environment\n- [ ] Product Owner accepted\n- [ ] No critical bugs remaining\n\n## Related Skills\n\n- **Scrum Master** (`project-management\u002Fscrum-master\u002F`) — Velocity data and sprint ceremonies complement backlog management\n- **Product Manager Toolkit** (`product-team\u002Fproduct-manager-toolkit\u002F`) — RICE prioritization feeds backlog ordering\n","# Agile Product Owner\n\nBacklog management and sprint execution toolkit for product owners, including user story generation, acceptance criteria patterns, sprint planning, and velocity tracking.\n\n---\n\n## Table of Contents\n\n- [What Makes This Skill Different](#what-makes-this-skill-different)\n- [User Story Generation Workflow](#user-story-generation-workflow)\n- [Acceptance Criteria Patterns](#acceptance-criteria-patterns)\n- [Epic Breakdown Workflow](#epic-breakdown-workflow)\n- [Sprint Planning Workflow](#sprint-planning-workflow)\n- [Backlog Prioritization](#backlog-prioritization)\n- [Reference Documentation](#reference-documentation)\n- [Tools](#tools)\n\n---\n\n## What Makes This Skill Different\n\n- **Capacity math that aligns with reality:** sprint capacity is based on velocity × availability factor, not hope.\n- **Acceptance criteria scaled by story size:** minimum AC counts map to story points to avoid under-spec'ing large items.\n- **Weighted prioritization that stays consistent:** value 40%, impact 30%, risk 15%, effort 15% keeps tradeoffs explicit.\n- **Systematic epic splitting techniques:** five concrete split patterns prevent oversized stories.\n- **INVEST validation baked into workflows:** every story includes a validation step, not just guidance.\n\n## User Story Generation Workflow\n\nCreate INVEST-compliant user stories from requirements:\n\n1. Identify the persona (who benefits from this feature)\n2. Define the action or capability needed\n3. Articulate the benefit or value delivered\n4. Write acceptance criteria using Given-When-Then\n5. Estimate story points using Fibonacci scale\n6. Validate against INVEST criteria\n7. Add to backlog with priority\n8. **Validation:** Story passes all INVEST criteria; acceptance criteria are testable\n\n### User Story Template\n\n```\nAs a [persona],\nI want to [action\u002Fcapability],\nSo that [benefit\u002Fvalue].\n```\n\n**Example:**\n```\nAs a marketing manager,\nI want to export campaign reports to PDF,\nSo that I can share results with stakeholders who don't have system access.\n```\n\n### Story Types\n\n| Type | Template | Example |\n|------|----------|---------|\n| 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 |\n| Improvement | As a [persona], I need [capability] to [goal] | As a user, I need faster page loads to complete tasks without frustration |\n| Bug Fix | As a [persona], I expect [behavior] when [condition] | As a user, I expect my cart to persist when I refresh the page |\n| Enabler | As a developer, I need to [technical task] to enable [capability] | As a developer, I need to implement caching to enable instant search |\n\n### Persona Reference\n\n| Persona | Typical Needs | Context |\n|---------|--------------|---------|\n| End User | Efficiency, simplicity, reliability | Daily feature usage |\n| Administrator | Control, visibility, security | System management |\n| Power User | Automation, customization, shortcuts | Expert workflows |\n| New User | Guidance, learning, safety | Onboarding |\n\n---\n\n## Acceptance Criteria Patterns\n\nWrite testable acceptance criteria using Given-When-Then format.\n\n### Given-When-Then Template\n\n```\nGiven [precondition\u002Fcontext],\nWhen [action\u002Ftrigger],\nThen [expected outcome].\n```\n\n**Examples:**\n```\nGiven the user is logged in with valid credentials,\nWhen they click the \"Export\" button,\nThen a PDF download starts within 2 seconds.\n\nGiven the user has entered an invalid email format,\nWhen they submit the registration form,\nThen an inline error message displays \"Please enter a valid email address.\"\n\nGiven the shopping cart contains items,\nWhen the user refreshes the browser,\nThen the cart contents remain unchanged.\n```\n\n### Acceptance Criteria Checklist\n\nEach story should include criteria for:\n\n| Category | Example |\n|----------|---------|\n| Happy Path | Given valid input, When submitted, Then success message displayed |\n| Validation | Should reject input when required field is empty |\n| Error Handling | Must show user-friendly message when API fails |\n| Performance | Should complete operation within 2 seconds |\n| Accessibility | Must be navigable via keyboard only |\n\n### Minimum Criteria by Story Size\n\n| Story Points | Minimum AC Count |\n|--------------|------------------|\n| 1-2 | 3-4 criteria |\n| 3-5 | 4-6 criteria |\n| 8 | 5-8 criteria |\n| 13+ | Split the story |\n\nSee `references\u002Fuser-story-templates.md` for complete template library.\n\n---\n\n## Epic Breakdown Workflow\n\nBreak epics into deliverable sprint-sized stories:\n\n1. Define epic scope and success criteria\n2. Identify all personas affected by the epic\n3. List all capabilities needed for each persona\n4. Group capabilities into logical stories\n5. Validate each story is ≤8 points\n6. Identify dependencies between stories\n7. Sequence stories for incremental delivery\n8. **Validation:** Each story delivers standalone value; total stories cover epic scope\n\n### Splitting Techniques\n\n| Technique | When to Use | Example |\n|-----------|-------------|---------|\n| By workflow step | Linear process | \"Checkout\" → \"Add to cart\" + \"Enter payment\" + \"Confirm order\" |\n| By persona | Multiple user types | \"Dashboard\" → \"Admin dashboard\" + \"User dashboard\" |\n| By data type | Multiple inputs | \"Import\" → \"Import CSV\" + \"Import Excel\" |\n| By operation | CRUD functionality | \"Manage users\" → \"Create\" + \"Edit\" + \"Delete\" |\n| Happy path first | Risk reduction | \"Feature\" → \"Basic flow\" + \"Error handling\" + \"Edge cases\" |\n\n### Epic Example\n\n**Epic:** User Dashboard\n\n**Breakdown:**\n```\nEpic: User Dashboard (34 points total)\n├── US-001: View key metrics (5 pts) - End User\n├── US-002: Customize layout (5 pts) - Power User\n├── US-003: Export data to CSV (3 pts) - End User\n├── US-004: Share with team (5 pts) - End User\n├── US-005: Set up alerts (5 pts) - Power User\n├── US-006: Filter by date range (3 pts) - End User\n├── US-007: Admin overview (5 pts) - Admin\n└── US-008: Enable caching (3 pts) - Enabler\n```\n\n---\n\n## Sprint Planning Workflow\n\nPlan sprint capacity and select stories:\n\n1. Calculate team capacity (velocity × availability)\n2. Review sprint goal with stakeholders\n3. Select stories from prioritized backlog\n4. Fill to 80-85% of capacity (committed)\n5. Add stretch goals (10-15% additional)\n6. Identify dependencies and risks\n7. Break complex stories into tasks\n8. **Validation:** Committed points ≤85% capacity; all stories have acceptance criteria\n\n### Capacity Calculation\n\n```\nSprint Capacity = Average Velocity × Availability Factor\n\nExample:\nAverage Velocity: 30 points\nTeam availability: 90% (one member partially out)\nAdjusted Capacity: 27 points\n\nCommitted: 23 points (85% of 27)\nStretch: 4 points (15% of 27)\n```\n\n### Availability Factors\n\n| Scenario | Factor |\n|----------|--------|\n| Full sprint, no PTO | 1.0 |\n| One team member out 50% | 0.9 |\n| Holiday during sprint | 0.8 |\n| Multiple members out | 0.7 |\n\n### Sprint Loading Template\n\n```\nSprint Capacity: 27 points\nSprint Goal: [Clear, measurable objective]\n\nCOMMITTED (23 points):\n[H] US-001: User dashboard (5 pts)\n[H] US-002: Export feature (3 pts)\n[H] US-003: Search filter (5 pts)\n[M] US-004: Settings page (5 pts)\n[M] US-005: Help tooltips (3 pts)\n[L] US-006: Theme options (2 pts)\n\nSTRETCH (4 points):\n[L] US-007: Sort options (2 pts)\n[L] US-008: Print view (2 pts)\n```\n\nSee `references\u002Fsprint-planning-guide.md` for complete planning procedures.\n\n---\n\n## Backlog Prioritization\n\nPrioritize backlog using value and effort assessment.\n\n### Priority Levels\n\n| Priority | Definition | Sprint Target |\n|----------|------------|---------------|\n| Critical | Blocking users, security, data loss | Immediate |\n| High | Core functionality, key user needs | This sprint |\n| Medium | Improvements, enhancements | Next 2-3 sprints |\n| Low | Nice-to-have, minor improvements | Backlog |\n\n### Prioritization Factors\n\n| Factor | Weight | Questions |\n|--------|--------|-----------|\n| Business Value | 40% | Revenue impact? User demand? Strategic alignment? |\n| User Impact | 30% | How many users? How frequently used? |\n| Risk\u002FDependencies | 15% | Technical risk? External dependencies? |\n| Effort | 15% | Size? Complexity? Uncertainty? |\n\n### INVEST Criteria Validation\n\nBefore adding to sprint, validate each story:\n\n| Criterion | Question | Pass If... |\n|-----------|----------|------------|\n| **I**ndependent | Can this be developed without other uncommitted stories? | No blocking dependencies |\n| **N**egotiable | Is the implementation flexible? | Multiple approaches possible |\n| **V**aluable | Does this deliver user or business value? | Clear benefit in \"so that\" |\n| **E**stimable | Can the team estimate this? | Understood well enough to size |\n| **S**mall | Can this complete in one sprint? | ≤8 story points |\n| **T**estable | Can we verify this is done? | Clear acceptance criteria |\n\n---\n\n## Reference Documentation\n\n### User Story Templates\n\n`references\u002Fuser-story-templates.md` contains:\n\n- Standard story formats by type (feature, improvement, bug fix, enabler)\n- Acceptance criteria patterns (Given-When-Then, Should\u002FMust\u002FCan)\n- INVEST criteria validation checklist\n- Story point estimation guide (Fibonacci scale)\n- Common story antipatterns and fixes\n- Story splitting techniques\n\n### Sprint Planning Guide\n\n`references\u002Fsprint-planning-guide.md` contains:\n\n- Sprint planning meeting agenda\n- Capacity calculation formulas\n- Backlog prioritization framework (WSJF)\n- Sprint ceremony guides (standup, review, retro)\n- Velocity tracking and burndown patterns\n- Definition of Done checklist\n- Sprint metrics and targets\n\n---\n\n## Tools\n\n### User Story Generator\n\n```bash\n# Generate stories from sample epic\npython scripts\u002Fuser_story_generator.py\n\n# Plan sprint with capacity\npython scripts\u002Fuser_story_generator.py sprint 30\n```\n\nGenerates:\n- INVEST-compliant user stories\n- Given-When-Then acceptance criteria\n- Story point estimates (Fibonacci scale)\n- Priority assignments\n- Sprint loading with committed and stretch items\n\n### Sample Output\n\n```\nUSER STORY: USR-001\n========================================\nTitle: View Key Metrics\nType: story\nPriority: HIGH\nPoints: 5\n\nStory:\nAs a End User, I want to view key metrics and KPIs\nso that I can save time and work more efficiently\n\nAcceptance Criteria:\n  1. Given user has access, When they view key metrics, Then the result is displayed\n  2. Should validate input before processing\n  3. Must show clear error message when action fails\n  4. Should complete within 2 seconds\n  5. Must be accessible via keyboard navigation\n\nINVEST Checklist:\n  ✓ Independent\n  ✓ Negotiable\n  ✓ Valuable\n  ✓ Estimable\n  ✓ Small\n  ✓ Testable\n```\n\n---\n\n## Sprint Metrics\n\nTrack sprint health and team performance.\n\n### Key Metrics\n\n| Metric | Formula | Target |\n|--------|---------|--------|\n| Velocity | Points completed \u002F sprint | Stable ±10% |\n| Commitment Reliability | Completed \u002F Committed | >85% |\n| Scope Change | Points added or removed mid-sprint | \u003C10% |\n| Carryover | Points not completed | \u003C15% |\n\n### Velocity Tracking\n\n```\nSprint 1: 25 points\nSprint 2: 28 points\nSprint 3: 30 points\nSprint 4: 32 points\nSprint 5: 29 points\n------------------------\nAverage Velocity: 28.8 points\nTrend: Stable\n\nPlanning: Commit to 24-26 points\n```\n\n### Definition of Done\n\nStory is complete when:\n\n- [ ] Code complete and peer reviewed\n- [ ] Unit tests written and passing\n- [ ] Acceptance criteria verified\n- [ ] Documentation updated\n- [ ] Deployed to staging environment\n- [ ] Product Owner accepted\n- [ ] No critical bugs remaining\n\n## Related Skills\n\n- **Scrum Master** (`project-management\u002Fscrum-master\u002F`) — Velocity data and sprint ceremonies complement backlog management\n- **Product Manager Toolkit** (`product-team\u002Fproduct-manager-toolkit\u002F`) — RICE prioritization feeds backlog ordering\n",{"name":5,"tags":48,"tools":49,"source":50,"license":14,"description":7,"source_path":51,"source_commit":52},[26,28,35],[],"https:\u002F\u002Fgithub.com\u002Falirezarezvani\u002Fclaude-skills","product-team\u002Fagile-product-owner\u002Fskills\u002Fagile-product-owner","19392f7a08264ed00486a251f5b2098321771f94","main","f7cd4595d0f8959822163e14f9787117765c931a","packages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner",2,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind","https:\u002F\u002Fmonoes.github.io\u002Fmonomind\u002F","https:\u002F\u002Fgithub.com\u002Fmonoes","https:\u002F\u002Fmonoes.me","2026-11-10 01:53:48",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add monoes\u002Fmonomind --skill agile-product-owner",{"tool":68,"command":69},"bunx","bunx skills add monoes\u002Fmonomind --skill agile-product-owner",{"tool":71,"command":72},"pnpm","pnpm dlx skills add monoes\u002Fmonomind --skill agile-product-owner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner\u002FSKILL.md",true,[76,82,86,91,97],{"path":77,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":80,"sourceHtmlUrl":81},"assets\u002Fsprint_planning_template.md","ASSET","资产文件",2328,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md",{"path":83,"resourceType":78,"resourceTypeDesc":79,"sizeBytes":84,"sourceHtmlUrl":85},"assets\u002Fuser_story_template.md",1278,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner\u002Fassets\u002Fuser_story_template.md",{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":15},"LICENSE.txt","LICENSE","许可证",1072,{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fsprint-planning-guide.md","REFERENCE","参考文档",8757,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md",{"path":98,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fuser-story-templates.md",8432,"https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md",[102,130,161,185,209,236],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":129},"01M71PB3SHWKMNJM6MD65VX8D6","zk-steward","Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fzk-steward\u002FSKILL.md",[],[110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,33,128],"zk","zk steward","steward","zero-knowledge","engineer","choice","design","knowledge","impact","query","snark","review","monomind","security review","stark","zettelkasten","cryptography","security","blockchain","2026-11-10 13:02:02",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":134,"sourceHtmlUrl":135,"categories":136,"keywords":145,"publishedAt":129},"01M71PB18SDG28WBKPKJNB814K","writing-plans","Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwriting-plans\u002FSKILL.md",[137,142],{"categoryNo":138,"categoryName":139,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":143,"categoryName":144,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[39,146,147,114,148,149,37,150,119,151,152,153,26,154,155,156,157,158,159,160],"writing plans","plans","superpowers","implementation plan","you","code","tasks","plan","write","commands","paths","suggest","coding","context","ZeRO",{"skillNo":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":165,"sourceHtmlUrl":166,"categories":167,"keywords":169,"publishedAt":129},"01M71PAXFM488X9ARXK0T04TF5","write-spec","Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-spec\u002FSKILL.md",[168],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[154,170,171,172,173,117,38,37,174,175,176,26,177,178,179,180,181,182,183,184],"write spec","spec","user request","problem","ask","vague","work","request","scoping","idea","metrics","feature","problem statement","use","document",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":189,"sourceHtmlUrl":190,"categories":191,"keywords":195,"publishedAt":129},"01M71PASSZY800C0RPEARBS918","write-query","Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fwrite-query\u002FSKILL.md",[192],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师",[119,154,196,197,27,198,117,183,37,199,200,201,202,176,203,204,205,206,207,208],"write query","postgres","snowflake","best practices","natural-language","with","multi","github","sql","https","syntax","plugins","data",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":221,"publishedAt":129},"01M71PAPTX0T3PF6ETFVR96SJJ","workflow-automation","Org role guidance for workflow automation: build and maintain CI\u002FCD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-automation\u002FSKILL.md",[215,218],{"categoryNo":216,"categoryName":217,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":219,"categoryName":220,"taxonomyType":140,"taxonomyTypeDesc":141},"01JBSEEDCAT000000000000023","Skill与智能体开发",[222,223,224,225,27,226,227,228,229,118,230,231,232,119,122,203,233,234,235,205],"Workflow Automation","automation","workflow","parallel","actions","ci","triggers","github actions","maintain","filters","caching","build","dependency","devops",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":106,"licenseFileUrl":6,"sourceHtmlUrl":240,"categories":241,"keywords":243,"publishedAt":129},"01M71PAM19Z1XTV9NPCFSE2MY8","workflow-architect","Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.","https:\u002F\u002Fgithub.com\u002Fmonoes\u002Fmonomind\u002Fblob\u002Fmain\u002Fpackages\u002F@monomind\u002Fcli\u002Forg-skills\u002Fworkflow-architect\u002FSKILL.md",[242],{"categoryNo":219,"categoryName":220,"taxonomyType":140,"taxonomyTypeDesc":141},[224,244,245,246,247,248,28,27,249,250,151,251,252,253,122,203,254,255,205,256],"workflow architect","architect","trees","user journeys","branch","map","workflows","architecture","state","leadership","recovery","operations","systems"]