[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6KBT96ZQVZBWS08DJDTBA31":3,"skill-same:01M6KBT96ZQVZBWS08DJDTBA31":110},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":65,"repositoryHtmlUrl":66,"repositoryHomepageUrl":6,"ownerHtmlUrl":67,"ownerBlogUrl":68,"ownerDescription":6,"updatedAt":69,"install":70,"resources":83},"01M6KBT96ZQVZBWS08DJDTBA31","agile-product-owner",null,"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.","afaizalam2003\u002FMaster-claude-skill","afaizalam2003","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F222019359?v=4","01M6K8F2XNT0HKBPF00JQ78SV3","Faiz Alam","01M6K8F31EBXAPER0EG8R9HTR5",3,"MIT","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\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,34,35,36,37,38,39,40,41,42,43],"agile","product","agile product owner","template","down","break","user stories","sprints","sprint","velocity","user story writing","user story","write","writing","prioritize","plan","acceptance","planning","create","backlog management","2026-11-10 10:12:30",false,"---\nname: \"agile-product-owner\"\ndescription: 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.\ntriggers:\n  - write user story\n  - create acceptance criteria\n  - plan sprint\n  - estimate story points\n  - break down epic\n  - prioritize backlog\n  - sprint planning\n  - INVEST criteria\n  - Given When Then\n  - user story template\n  - sprint capacity\n  - velocity tracking\n---\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- [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## 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- [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## 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,"triggers":49,"description":7},[50,51,52,53,54,55,56,57,58,59,60,61],"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","main","0b48cbb0e6d5be6ff68c0f6b28bc0c65ee21c4a1","product-team\u002Fagile-product-owner",2,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill","https:\u002F\u002Fgithub.com\u002Fafaizalam2003","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fmdfaizalam2003\u002F","2026-04-01 04:35:43",{"source":8,"skillName":5,"commands":71,"prompt":81,"zipAvailable":82},[72,75,78],{"tool":73,"command":74},"npx","npx skills add afaizalam2003\u002FMaster-claude-skill --skill agile-product-owner",{"tool":76,"command":77},"bunx","bunx skills add afaizalam2003\u002FMaster-claude-skill --skill agile-product-owner",{"tool":79,"command":80},"pnpm","pnpm dlx skills add afaizalam2003\u002FMaster-claude-skill --skill agile-product-owner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fagile-product-owner\u002FSKILL.md",true,[84,90,94,100,104],{"path":85,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":88,"sourceHtmlUrl":89},"assets\u002Fsprint_planning_template.md","ASSET","资产文件",2328,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md",{"path":91,"resourceType":86,"resourceTypeDesc":87,"sizeBytes":92,"sourceHtmlUrl":93},"assets\u002Fuser_story_template.md",1278,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fuser_story_template.md",{"path":95,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Fsprint-planning-guide.md","REFERENCE","参考文档",8757,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md",{"path":101,"resourceType":96,"resourceTypeDesc":97,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fuser-story-templates.md",8432,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Fuser_story_generator.py","SCRIPT","脚本",14969,"https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py",[111,141,165,188,220,240],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":120,"publishedAt":44},"01M6KC4E8MYR9DBAZTAXHKYMMH","soc2-compliance","Use when the user asks to prepare for SOC 2 audits, map Trust Service Criteria, build control matrices, collect audit evidence, perform gap analysis, or assess SOC 2 Type I vs Type II readiness.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fsoc2-compliance\u002FSKILL.md",[117],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务",[121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140],"compliance","soc2","soc2 compliance","audit evidence","audit","collect","soc","analysis","use","evidence","trust","build","map","control","type","gap","readiness","gap analysis","assess","for",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":44},"01M6KC461R3GKGZ1TAYHVR1MW9","risk-management-specialist","Medical device risk management specialist implementing ISO 14971 throughout product lifecycle. Provides risk analysis, risk evaluation, risk control, and post-production information analysis. Use when user mentions risk management, ISO 14971, risk analysis, FMEA, fault tree analysis, hazard identification, risk control, risk matrix, benefit-risk analysis, residual risk, risk acceptability, or post-market risk.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Frisk-management-specialist\u002FSKILL.md",[],[148,149,150,151,152,25,153,154,128,129,155,156,157,158,159,160,161,162,163,164],"risk","risk management specialist","management","risk management","risk evaluation","Evaluation","lifecycle","risk matrix","iso","medical","iso 14971","identification","information","post-production","tree","matrix","implementing",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":44},"01M6KC3HF5ZFSSP2NZF68PEPFB","regulatory-affairs-head","Senior Regulatory Affairs Manager for HealthTech and MedTech companies. Prepares FDA 510(k), De Novo, and PMA submission packages; analyzes regulatory pathways for new medical devices; drafts responses to FDA deficiency letters and Notified Body queries; develops CE marking technical documentation under EU MDR 2017\u002F745; coordinates multi-market approval strategies across FDA, EU, Health Canada, PMDA, and NMPA; and maintains regulatory intelligence on evolving standards. Use when users need to plan or execute FDA submissions, navigate 510(k) or PMA approval processes, achieve CE marking, prepare pre-submission meeting materials, write regulatory strategy documents, respond to agency queries, or manage compliance documentation for medical device market access.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fregulatory-affairs-head\u002FSKILL.md",[],[172,173,174,175,176,177,39,36,178,129,179,180,181,182,183,184,185,186,187,140],"regulatory affairs head","regulatory","head","documents","devices","health","strategy","standards","queries","manage","strategies","de","users","respond","medical devices","manager",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":202,"publishedAt":44},"01M6KC34Z8M1559EY1CXYBJB1A","quality-manager-qms-iso13485","ISO 13485 Quality Management System implementation and maintenance for medical device organizations. Provides QMS design, documentation control, internal auditing, CAPA management, and certification support. Use when working with medical device quality systems, preparing for ISO 13485 audits, managing regulatory compliance documentation, setting up corrective actions, or building audit preparation programs. Useful for quality management, audit preparation, regulatory compliance, medical device documentation, and corrective action workflows.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qms-iso13485\u002FSKILL.md",[194,199],{"categoryNo":195,"categoryName":196,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":200,"categoryName":201,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000032","设计师",[203,204,187,205,206,207,208,209,210,129,211,212,213,214,215,216,217,218,140,219],"quality manager qms iso13485","quality","design","workflows","validation","actions","certification","system","maintenance","document","systems","records","ISO 13485","organizations","corrective action","internal audit","preparation",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":227,"publishedAt":44},"01M6KC2FXHBHXYX2ZZ17Y3GDB4","quality-manager-qmr","Senior Quality Manager Responsible Person (QMR) for HealthTech and MedTech companies. Provides quality system governance, management review leadership, regulatory compliance oversight, and quality performance monitoring per ISO 13485 Clause 5.5.2.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-manager-qmr\u002FSKILL.md",[226],{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},[228,204,187,229,230,231,232,233,121,234,210,235,173,236,237,238,156,215,140,239],"quality manager qmr","review","policy","performance","governance","monitoring","regulatory compliance","oversight","cost","culture","leadership","person",{"skillNo":241,"name":242,"nameZh":6,"description":243,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":244,"categories":245,"keywords":253,"publishedAt":44},"01M6KC1VRR5JTDBNZANHPS6VR6","quality-documentation-manager","Document control system management for medical device QMS. Covers document numbering, version control, change management, and 21 CFR Part 11 compliance. Use for document control procedures, change control workflow, document numbering, version management, electronic signature compliance, or regulatory documentation review.","https:\u002F\u002Fgithub.com\u002Fafaizalam2003\u002FMaster-claude-skill\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fquality-documentation-manager\u002FSKILL.md",[246,249,252],{"categoryNo":247,"categoryName":248,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":250,"categoryName":251,"taxonomyType":197,"taxonomyTypeDesc":198},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":118,"categoryName":119,"taxonomyType":21,"taxonomyTypeDesc":22},[254,255,204,187,229,256,257,125,210,258,259,260,261,262,157,263,264,265,266,140],"documentation","quality documentation manager","workflow","change","change management","list","master","system management","documentation review","cfr","21 cfr part 11","change control","retention"]