[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CN6HWNEW5B7WSH6P8YAM7":3,"skill-same:01M75CN6HWNEW5B7WSH6P8YAM7":55},{"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":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":35,"repositoryHtmlUrl":36,"repositoryHomepageUrl":37,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M75CN6HWNEW5B7WSH6P8YAM7","cs-agile-product-owner",null,"Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcs-agile-product-owner\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: cs-agile-product-owner\ndescription: Agile product owner agent for epic breakdown, sprint planning, backlog refinement, and INVEST-compliant user story generation\nskills: product-team\u002Fagile-product-owner, product-team\u002Fproduct-manager-toolkit\ndomain: product\nmodel: sonnet\ntools: [Read, Write, Bash, Grep, Glob]\n---\n\n# Agile Product Owner Agent\n\n## Purpose\n\nThe cs-agile-product-owner agent is a specialized agile product ownership agent focused on backlog management, sprint planning, user story creation, and epic decomposition. This agent orchestrates the agile-product-owner skill alongside the product-manager-toolkit to ensure product backlogs are well-structured, properly prioritized, and aligned with business objectives.\n\nThis agent is designed for product owners, scrum masters wearing the PO hat, and agile team leads who need structured processes for breaking down epics into deliverable user stories, running effective sprint planning sessions, and maintaining a healthy product backlog. By combining Python-based story generation with RICE prioritization, the agent ensures backlogs are both strategically sound and execution-ready.\n\nThe cs-agile-product-owner agent bridges strategic product goals with sprint-level execution, providing frameworks for translating roadmap items into well-defined, INVEST-compliant user stories with clear acceptance criteria. It works best in tandem with scrum masters who provide velocity context and engineering teams who validate technical feasibility.\n\n## Skill Integration\n\n**Primary Skill:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002F`\n\n### All Orchestrated Skills\n\n| # | Skill | Location | Primary Tool |\n|---|-------|----------|-------------|\n| 1 | Agile Product Owner | `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002F` | user_story_generator.py |\n| 2 | Product Manager Toolkit | `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002F` | rice_prioritizer.py |\n\n### Python Tools\n\n1. **User Story Generator**\n   - **Purpose:** Break epics into INVEST-compliant user stories with acceptance criteria in Given\u002FWhen\u002FThen format\n   - **Path:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py`\n   - **Usage:** `python ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py epic.yaml`\n   - **Features:** Epic decomposition, acceptance criteria generation, story point estimation, dependency mapping\n   - **Use Cases:** Sprint planning, backlog refinement, story writing workshops\n\n2. **RICE Prioritizer**\n   - **Purpose:** RICE framework for backlog prioritization with portfolio analysis\n   - **Path:** `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py`\n   - **Usage:** `python ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv --capacity 20`\n   - **Features:** Portfolio quadrant analysis, capacity planning, quarterly roadmap generation\n   - **Use Cases:** Backlog ordering, sprint scope decisions, stakeholder alignment\n\n### Knowledge Bases\n\n1. **Sprint Planning Guide**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md`\n   - **Content:** Sprint planning ceremonies, velocity tracking, capacity allocation, sprint goal setting\n   - **Use Case:** Sprint planning facilitation, capacity management\n\n2. **User Story Templates**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md`\n   - **Content:** INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques\n   - **Use Case:** Story writing, backlog grooming, definition of done\n\n3. **PRD Templates**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Freferences\u002Fprd_templates.md`\n   - **Content:** Product requirements document formats for different complexity levels\n   - **Use Case:** Epic documentation, feature specification\n\n### Templates\n\n1. **Sprint Planning Template**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md`\n   - **Use Case:** Sprint planning sessions, capacity tracking, sprint goal documentation\n\n2. **User Story Template**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fuser_story_template.md`\n   - **Use Case:** Consistent story format, acceptance criteria structure\n\n3. **RICE Input Template**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fassets\u002Frice_input_template.csv`\n   - **Use Case:** Structuring backlog items for RICE prioritization\n\n## Workflows\n\n### Workflow 1: Epic Breakdown\n\n**Goal:** Decompose a large epic into sprint-ready user stories with acceptance criteria\n\n**Steps:**\n1. **Define the Epic** - Document the epic with clear scope:\n   - Business objective and user value\n   - Target user persona(s)\n   - High-level acceptance criteria\n   - Known constraints and dependencies\n\n2. **Create Epic YAML** - Structure the epic for the story generator:\n   ```yaml\n   epic:\n     title: \"User Dashboard\"\n     description: \"Comprehensive dashboard for user activity and metrics\"\n     personas: [\"admin\", \"standard-user\"]\n     features:\n       - \"Activity feed\"\n       - \"Usage metrics\"\n       - \"Settings panel\"\n   ```\n\n3. **Generate Stories** - Run the user story generator:\n   ```bash\n   python ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py epic.yaml\n   ```\n\n4. **Review and Refine** - For each generated story:\n   - Validate INVEST compliance (Independent, Negotiable, Valuable, Estimable, Small, Testable)\n   - Refine acceptance criteria (Given\u002FWhen\u002FThen format)\n   - Identify dependencies between stories\n   - Estimate story points with the team\n\n5. **Order the Backlog** - Sequence stories for delivery:\n   - Must-have stories first (MVP)\n   - Group by dependency chain\n   - Balance technical and user-facing work\n\n**Expected Output:** 8-15 well-defined user stories per epic with acceptance criteria, story points, and dependency map\n\n**Time Estimate:** 2-4 hours per epic\n\n**Example:**\n```bash\n# Create epic definition\ncat > dashboard-epic.yaml \u003C\u003C 'EOF'\nepic:\n  title: \"User Dashboard\"\n  description: \"Real-time dashboard showing user activity, key metrics, and account settings\"\n  personas: [\"admin\", \"standard-user\"]\n  features:\n    - \"Real-time activity feed\"\n    - \"Key metrics display with charts\"\n    - \"Quick settings access\"\n    - \"Notification preferences\"\nEOF\n\n# Generate user stories\npython ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py dashboard-epic.yaml\n\n# Review the sprint planning guide for context\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md\n```\n\n### Workflow 2: Sprint Planning\n\n**Goal:** Plan a sprint with clear goals, selected stories, and identified risks\n\n**Steps:**\n1. **Calculate Capacity** - Determine team availability:\n   - List team members and available days\n   - Account for PTO, on-call, training, meetings\n   - Calculate total person-days\n   - Reference historical velocity (average of last 3 sprints)\n\n2. **Review Backlog** - Ensure stories are ready:\n   - Check Definition of Ready for top candidates\n   - Verify acceptance criteria are complete\n   - Confirm technical feasibility with engineers\n   - Identify any blocking dependencies\n\n3. **Set Sprint Goal** - Define one clear, measurable goal:\n   - Aligned with quarterly OKRs\n   - Achievable within sprint capacity\n   - Valuable to users or business\n\n4. **Select Stories** - Pull from prioritized backlog:\n   ```bash\n   # Prioritize candidates if not already ordered\n   python ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py sprint-candidates.csv --capacity 12\n   ```\n\n5. **Document the Plan** - Use the sprint planning template:\n   ```bash\n   cat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md\n   ```\n\n6. **Identify Risks** - Document potential blockers:\n   - External dependencies\n   - Technical unknowns\n   - Team availability changes\n   - Mitigation plans for each risk\n\n**Expected Output:** Sprint plan document with goal, selected stories (within velocity), capacity allocation, dependencies, and risks\n\n**Time Estimate:** 2-3 hours per sprint planning session\n\n**Example:**\n```bash\n# Prepare sprint candidates\ncat > sprint-candidates.csv \u003C\u003C 'EOF'\nfeature,reach,impact,confidence,effort\nUser Dashboard - Activity Feed,500,3,0.8,3\nUser Dashboard - Metrics Charts,500,2,0.9,5\nNotification Preferences,300,1,1.0,2\nPassword Reset Flow Fix,1000,2,1.0,1\nEOF\n\n# Run prioritization\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py sprint-candidates.csv --capacity 8\n\n# Reference sprint planning template\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md\n```\n\n### Workflow 3: Backlog Refinement\n\n**Goal:** Maintain a healthy backlog with properly sized, prioritized, and well-defined stories\n\n**Steps:**\n1. **Triage New Items** - Process incoming requests:\n   - Customer feedback items\n   - Bug reports\n   - Technical debt tickets\n   - Feature requests from stakeholders\n\n2. **Size and Estimate** - Apply story points:\n   - Use planning poker or T-shirt sizing\n   - Reference team estimation guidelines\n   - Split stories larger than 13 story points\n   - Apply story splitting techniques from references\n\n3. **Prioritize with RICE** - Score backlog items:\n   ```bash\n   python ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv\n   ```\n\n4. **Refine Top Items** - Ensure top 2 sprints worth are ready:\n   - Complete acceptance criteria\n   - Resolve open questions with stakeholders\n   - Add technical notes and implementation hints\n   - Verify designs are available (if applicable)\n\n5. **Archive or Remove** - Clean the backlog:\n   - Close items older than 6 months without activity\n   - Merge duplicate stories\n   - Remove items no longer aligned with strategy\n\n**Expected Output:** Refined backlog with top 20 stories fully defined, estimated, and ordered\n\n**Time Estimate:** 1-2 hours per weekly refinement session\n\n**Example:**\n```bash\n# Export backlog for prioritization\ncat > backlog-q2.csv \u003C\u003C 'EOF'\nfeature,reach,impact,confidence,effort\nSearch Improvement,800,3,0.8,5\nMobile Responsive Tables,600,2,0.7,3\nAPI Rate Limiting,400,2,0.9,2\nOnboarding Wizard,1000,3,0.6,8\nExport to PDF,200,1,1.0,1\nDark Mode,300,1,0.8,3\nEOF\n\n# Run full prioritization with capacity\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog-q2.csv --capacity 15\n\n# Review user story templates for refinement\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md\n```\n\n### Workflow 4: Story Writing Workshop\n\n**Goal:** Collaboratively write high-quality user stories with the team\n\n**Steps:**\n1. **Prepare the Session** - Gather inputs:\n   - Epic or feature description\n   - User personas involved\n   - Design mockups or wireframes\n   - Technical constraints\n\n2. **Identify User Personas** - Map stories to personas:\n   - Who are the primary users?\n   - What are their goals?\n   - What are their constraints?\n\n3. **Write Stories Collaboratively** - Use the template:\n   ```bash\n   cat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fuser_story_template.md\n   ```\n   - \"As a [persona], I want [capability], so that [benefit]\"\n   - Focus on user value, not implementation details\n   - One story per distinct user action or outcome\n\n4. **Add Acceptance Criteria** - Define \"done\":\n   - Given\u002FWhen\u002FThen format for each scenario\n   - Cover happy path, edge cases, and error states\n   - Include performance and accessibility requirements\n\n5. **Validate INVEST** - Check each story:\n   - **Independent**: Can be delivered without other stories\n   - **Negotiable**: Implementation details flexible\n   - **Valuable**: Delivers user or business value\n   - **Estimable**: Team can estimate effort\n   - **Small**: Fits within a single sprint\n   - **Testable**: Clear pass\u002Ffail criteria\n\n6. **Estimate as a Team** - Story point consensus:\n   - Use planning poker or fist of five\n   - Discuss outlier estimates\n   - Re-split if estimate exceeds 13 points\n\n**Expected Output:** Set of INVEST-compliant user stories with acceptance criteria and estimates\n\n**Time Estimate:** 1-2 hours per workshop (covering 1 epic or feature area)\n\n**Example:**\n```bash\n# Generate initial story candidates from epic\npython ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py feature-epic.yaml\n\n# Reference story templates for format guidance\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md\n\n# Reference sprint planning guide for estimation practices\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md\n```\n\n## Integration Examples\n\n### Example 1: End-to-End Sprint Cycle\n\n```bash\n#!\u002Fbin\u002Fbash\n# sprint-cycle.sh - Complete sprint planning automation\n\nSPRINT_NUM=14\nCAPACITY=12  # person-days equivalent in story points\n\necho \"Sprint $SPRINT_NUM Planning\"\necho \"==========================\"\n\n# Step 1: Prioritize backlog\necho \"\"\necho \"1. Backlog Prioritization:\"\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv --capacity $CAPACITY\n\n# Step 2: Generate stories for top epic\necho \"\"\necho \"2. Story Generation for Top Epic:\"\npython ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py top-epic.yaml\n\n# Step 3: Reference planning template\necho \"\"\necho \"3. Sprint Planning Template:\"\necho \"See: ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md\"\n```\n\n### Example 2: Backlog Health Check\n\n```bash\n#!\u002Fbin\u002Fbash\n# backlog-health.sh - Weekly backlog health assessment\n\necho \"Backlog Health Check - $(date +%Y-%m-%d)\"\necho \"========================================\"\n\n# Count stories by status\necho \"\"\necho \"Backlog Items:\"\nwc -l \u003C backlog.csv\necho \"items in backlog\"\n\n# Run prioritization\necho \"\"\necho \"Current Priorities:\"\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv --capacity 20\n\n# Check story templates\necho \"\"\necho \"Story Template Reference:\"\necho \"Location: ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md\"\n```\n\n## Success Metrics\n\n**Backlog Quality:**\n- **Story Readiness:** >80% of sprint candidates meet Definition of Ready\n- **Estimation Accuracy:** Actual effort within 20% of estimate (rolling average)\n- **Story Size:** \u003C5% of stories exceed 13 story points\n- **Acceptance Criteria:** 100% of stories have testable acceptance criteria\n\n**Sprint Execution:**\n- **Sprint Goal Achievement:** >85% of sprints meet their stated goal\n- **Velocity Stability:** Velocity variance \u003C20% sprint-to-sprint\n- **Scope Change:** \u003C10% scope change after sprint planning\n- **Completion Rate:** >90% of committed stories completed per sprint\n\n**Stakeholder Value:**\n- **Value Delivery:** Every sprint delivers demonstrable user value\n- **Cycle Time:** Average story cycle time \u003C5 days\n- **Lead Time:** Epic to delivery \u003C6 weeks average\n- **Stakeholder Satisfaction:** >4\u002F5 on sprint review feedback\n\n## Related Agents\n\n- [cs-product-manager](cs-product-manager.md) - Full product management lifecycle (RICE, interviews, PRDs)\n- [cs-product-strategist](cs-product-strategist.md) - OKR cascade and strategic planning for roadmap alignment\n- [cs-ux-researcher](cs-ux-researcher.md) - User research to inform story requirements and acceptance criteria\n- Scrum Master - Velocity context and sprint execution (see `..\u002F..\u002Fproject-management\u002Fscrum-master\u002F`)\n\n## References\n\n- **Primary Skill:** [..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002FSKILL.md](..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002FSKILL.md)\n- **RICE Framework:** [..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002FSKILL.md](..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002FSKILL.md)\n- **Product Domain Guide:** [..\u002F..\u002Fproduct-team\u002FCLAUDE.md](..\u002F..\u002Fproduct-team\u002FCLAUDE.md)\n- **Agent Development Guide:** [..\u002FCLAUDE.md](..\u002FCLAUDE.md)\n- **Scrum Master Skill:** [..\u002F..\u002Fproject-management\u002Fscrum-master\u002FSKILL.md](..\u002F..\u002Fproject-management\u002Fscrum-master\u002FSKILL.md)\n\n---\n\n**Last Updated:** March 9, 2026\n**Status:** Production Ready\n**Version:** 1.0\n","# Agile Product Owner Agent\n\n## Purpose\n\nThe cs-agile-product-owner agent is a specialized agile product ownership agent focused on backlog management, sprint planning, user story creation, and epic decomposition. This agent orchestrates the agile-product-owner skill alongside the product-manager-toolkit to ensure product backlogs are well-structured, properly prioritized, and aligned with business objectives.\n\nThis agent is designed for product owners, scrum masters wearing the PO hat, and agile team leads who need structured processes for breaking down epics into deliverable user stories, running effective sprint planning sessions, and maintaining a healthy product backlog. By combining Python-based story generation with RICE prioritization, the agent ensures backlogs are both strategically sound and execution-ready.\n\nThe cs-agile-product-owner agent bridges strategic product goals with sprint-level execution, providing frameworks for translating roadmap items into well-defined, INVEST-compliant user stories with clear acceptance criteria. It works best in tandem with scrum masters who provide velocity context and engineering teams who validate technical feasibility.\n\n## Skill Integration\n\n**Primary Skill:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002F`\n\n### All Orchestrated Skills\n\n| # | Skill | Location | Primary Tool |\n|---|-------|----------|-------------|\n| 1 | Agile Product Owner | `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002F` | user_story_generator.py |\n| 2 | Product Manager Toolkit | `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002F` | rice_prioritizer.py |\n\n### Python Tools\n\n1. **User Story Generator**\n   - **Purpose:** Break epics into INVEST-compliant user stories with acceptance criteria in Given\u002FWhen\u002FThen format\n   - **Path:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py`\n   - **Usage:** `python ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py epic.yaml`\n   - **Features:** Epic decomposition, acceptance criteria generation, story point estimation, dependency mapping\n   - **Use Cases:** Sprint planning, backlog refinement, story writing workshops\n\n2. **RICE Prioritizer**\n   - **Purpose:** RICE framework for backlog prioritization with portfolio analysis\n   - **Path:** `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py`\n   - **Usage:** `python ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv --capacity 20`\n   - **Features:** Portfolio quadrant analysis, capacity planning, quarterly roadmap generation\n   - **Use Cases:** Backlog ordering, sprint scope decisions, stakeholder alignment\n\n### Knowledge Bases\n\n1. **Sprint Planning Guide**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md`\n   - **Content:** Sprint planning ceremonies, velocity tracking, capacity allocation, sprint goal setting\n   - **Use Case:** Sprint planning facilitation, capacity management\n\n2. **User Story Templates**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md`\n   - **Content:** INVEST-compliant story formats, acceptance criteria patterns, story splitting techniques\n   - **Use Case:** Story writing, backlog grooming, definition of done\n\n3. **PRD Templates**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Freferences\u002Fprd_templates.md`\n   - **Content:** Product requirements document formats for different complexity levels\n   - **Use Case:** Epic documentation, feature specification\n\n### Templates\n\n1. **Sprint Planning Template**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md`\n   - **Use Case:** Sprint planning sessions, capacity tracking, sprint goal documentation\n\n2. **User Story Template**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fuser_story_template.md`\n   - **Use Case:** Consistent story format, acceptance criteria structure\n\n3. **RICE Input Template**\n   - **Location:** `..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fassets\u002Frice_input_template.csv`\n   - **Use Case:** Structuring backlog items for RICE prioritization\n\n## Workflows\n\n### Workflow 1: Epic Breakdown\n\n**Goal:** Decompose a large epic into sprint-ready user stories with acceptance criteria\n\n**Steps:**\n1. **Define the Epic** - Document the epic with clear scope:\n   - Business objective and user value\n   - Target user persona(s)\n   - High-level acceptance criteria\n   - Known constraints and dependencies\n\n2. **Create Epic YAML** - Structure the epic for the story generator:\n   ```yaml\n   epic:\n     title: \"User Dashboard\"\n     description: \"Comprehensive dashboard for user activity and metrics\"\n     personas: [\"admin\", \"standard-user\"]\n     features:\n       - \"Activity feed\"\n       - \"Usage metrics\"\n       - \"Settings panel\"\n   ```\n\n3. **Generate Stories** - Run the user story generator:\n   ```bash\n   python ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py epic.yaml\n   ```\n\n4. **Review and Refine** - For each generated story:\n   - Validate INVEST compliance (Independent, Negotiable, Valuable, Estimable, Small, Testable)\n   - Refine acceptance criteria (Given\u002FWhen\u002FThen format)\n   - Identify dependencies between stories\n   - Estimate story points with the team\n\n5. **Order the Backlog** - Sequence stories for delivery:\n   - Must-have stories first (MVP)\n   - Group by dependency chain\n   - Balance technical and user-facing work\n\n**Expected Output:** 8-15 well-defined user stories per epic with acceptance criteria, story points, and dependency map\n\n**Time Estimate:** 2-4 hours per epic\n\n**Example:**\n```bash\n# Create epic definition\ncat > dashboard-epic.yaml \u003C\u003C 'EOF'\nepic:\n  title: \"User Dashboard\"\n  description: \"Real-time dashboard showing user activity, key metrics, and account settings\"\n  personas: [\"admin\", \"standard-user\"]\n  features:\n    - \"Real-time activity feed\"\n    - \"Key metrics display with charts\"\n    - \"Quick settings access\"\n    - \"Notification preferences\"\nEOF\n\n# Generate user stories\npython ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py dashboard-epic.yaml\n\n# Review the sprint planning guide for context\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md\n```\n\n### Workflow 2: Sprint Planning\n\n**Goal:** Plan a sprint with clear goals, selected stories, and identified risks\n\n**Steps:**\n1. **Calculate Capacity** - Determine team availability:\n   - List team members and available days\n   - Account for PTO, on-call, training, meetings\n   - Calculate total person-days\n   - Reference historical velocity (average of last 3 sprints)\n\n2. **Review Backlog** - Ensure stories are ready:\n   - Check Definition of Ready for top candidates\n   - Verify acceptance criteria are complete\n   - Confirm technical feasibility with engineers\n   - Identify any blocking dependencies\n\n3. **Set Sprint Goal** - Define one clear, measurable goal:\n   - Aligned with quarterly OKRs\n   - Achievable within sprint capacity\n   - Valuable to users or business\n\n4. **Select Stories** - Pull from prioritized backlog:\n   ```bash\n   # Prioritize candidates if not already ordered\n   python ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py sprint-candidates.csv --capacity 12\n   ```\n\n5. **Document the Plan** - Use the sprint planning template:\n   ```bash\n   cat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md\n   ```\n\n6. **Identify Risks** - Document potential blockers:\n   - External dependencies\n   - Technical unknowns\n   - Team availability changes\n   - Mitigation plans for each risk\n\n**Expected Output:** Sprint plan document with goal, selected stories (within velocity), capacity allocation, dependencies, and risks\n\n**Time Estimate:** 2-3 hours per sprint planning session\n\n**Example:**\n```bash\n# Prepare sprint candidates\ncat > sprint-candidates.csv \u003C\u003C 'EOF'\nfeature,reach,impact,confidence,effort\nUser Dashboard - Activity Feed,500,3,0.8,3\nUser Dashboard - Metrics Charts,500,2,0.9,5\nNotification Preferences,300,1,1.0,2\nPassword Reset Flow Fix,1000,2,1.0,1\nEOF\n\n# Run prioritization\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py sprint-candidates.csv --capacity 8\n\n# Reference sprint planning template\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md\n```\n\n### Workflow 3: Backlog Refinement\n\n**Goal:** Maintain a healthy backlog with properly sized, prioritized, and well-defined stories\n\n**Steps:**\n1. **Triage New Items** - Process incoming requests:\n   - Customer feedback items\n   - Bug reports\n   - Technical debt tickets\n   - Feature requests from stakeholders\n\n2. **Size and Estimate** - Apply story points:\n   - Use planning poker or T-shirt sizing\n   - Reference team estimation guidelines\n   - Split stories larger than 13 story points\n   - Apply story splitting techniques from references\n\n3. **Prioritize with RICE** - Score backlog items:\n   ```bash\n   python ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv\n   ```\n\n4. **Refine Top Items** - Ensure top 2 sprints worth are ready:\n   - Complete acceptance criteria\n   - Resolve open questions with stakeholders\n   - Add technical notes and implementation hints\n   - Verify designs are available (if applicable)\n\n5. **Archive or Remove** - Clean the backlog:\n   - Close items older than 6 months without activity\n   - Merge duplicate stories\n   - Remove items no longer aligned with strategy\n\n**Expected Output:** Refined backlog with top 20 stories fully defined, estimated, and ordered\n\n**Time Estimate:** 1-2 hours per weekly refinement session\n\n**Example:**\n```bash\n# Export backlog for prioritization\ncat > backlog-q2.csv \u003C\u003C 'EOF'\nfeature,reach,impact,confidence,effort\nSearch Improvement,800,3,0.8,5\nMobile Responsive Tables,600,2,0.7,3\nAPI Rate Limiting,400,2,0.9,2\nOnboarding Wizard,1000,3,0.6,8\nExport to PDF,200,1,1.0,1\nDark Mode,300,1,0.8,3\nEOF\n\n# Run full prioritization with capacity\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog-q2.csv --capacity 15\n\n# Review user story templates for refinement\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md\n```\n\n### Workflow 4: Story Writing Workshop\n\n**Goal:** Collaboratively write high-quality user stories with the team\n\n**Steps:**\n1. **Prepare the Session** - Gather inputs:\n   - Epic or feature description\n   - User personas involved\n   - Design mockups or wireframes\n   - Technical constraints\n\n2. **Identify User Personas** - Map stories to personas:\n   - Who are the primary users?\n   - What are their goals?\n   - What are their constraints?\n\n3. **Write Stories Collaboratively** - Use the template:\n   ```bash\n   cat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fuser_story_template.md\n   ```\n   - \"As a [persona], I want [capability], so that [benefit]\"\n   - Focus on user value, not implementation details\n   - One story per distinct user action or outcome\n\n4. **Add Acceptance Criteria** - Define \"done\":\n   - Given\u002FWhen\u002FThen format for each scenario\n   - Cover happy path, edge cases, and error states\n   - Include performance and accessibility requirements\n\n5. **Validate INVEST** - Check each story:\n   - **Independent**: Can be delivered without other stories\n   - **Negotiable**: Implementation details flexible\n   - **Valuable**: Delivers user or business value\n   - **Estimable**: Team can estimate effort\n   - **Small**: Fits within a single sprint\n   - **Testable**: Clear pass\u002Ffail criteria\n\n6. **Estimate as a Team** - Story point consensus:\n   - Use planning poker or fist of five\n   - Discuss outlier estimates\n   - Re-split if estimate exceeds 13 points\n\n**Expected Output:** Set of INVEST-compliant user stories with acceptance criteria and estimates\n\n**Time Estimate:** 1-2 hours per workshop (covering 1 epic or feature area)\n\n**Example:**\n```bash\n# Generate initial story candidates from epic\npython ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py feature-epic.yaml\n\n# Reference story templates for format guidance\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md\n\n# Reference sprint planning guide for estimation practices\ncat ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fsprint-planning-guide.md\n```\n\n## Integration Examples\n\n### Example 1: End-to-End Sprint Cycle\n\n```bash\n#!\u002Fbin\u002Fbash\n# sprint-cycle.sh - Complete sprint planning automation\n\nSPRINT_NUM=14\nCAPACITY=12  # person-days equivalent in story points\n\necho \"Sprint $SPRINT_NUM Planning\"\necho \"==========================\"\n\n# Step 1: Prioritize backlog\necho \"\"\necho \"1. Backlog Prioritization:\"\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv --capacity $CAPACITY\n\n# Step 2: Generate stories for top epic\necho \"\"\necho \"2. Story Generation for Top Epic:\"\npython ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fscripts\u002Fuser_story_generator.py top-epic.yaml\n\n# Step 3: Reference planning template\necho \"\"\necho \"3. Sprint Planning Template:\"\necho \"See: ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Fassets\u002Fsprint_planning_template.md\"\n```\n\n### Example 2: Backlog Health Check\n\n```bash\n#!\u002Fbin\u002Fbash\n# backlog-health.sh - Weekly backlog health assessment\n\necho \"Backlog Health Check - $(date +%Y-%m-%d)\"\necho \"========================================\"\n\n# Count stories by status\necho \"\"\necho \"Backlog Items:\"\nwc -l \u003C backlog.csv\necho \"items in backlog\"\n\n# Run prioritization\necho \"\"\necho \"Current Priorities:\"\npython ..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002Fscripts\u002Frice_prioritizer.py backlog.csv --capacity 20\n\n# Check story templates\necho \"\"\necho \"Story Template Reference:\"\necho \"Location: ..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002Freferences\u002Fuser-story-templates.md\"\n```\n\n## Success Metrics\n\n**Backlog Quality:**\n- **Story Readiness:** >80% of sprint candidates meet Definition of Ready\n- **Estimation Accuracy:** Actual effort within 20% of estimate (rolling average)\n- **Story Size:** \u003C5% of stories exceed 13 story points\n- **Acceptance Criteria:** 100% of stories have testable acceptance criteria\n\n**Sprint Execution:**\n- **Sprint Goal Achievement:** >85% of sprints meet their stated goal\n- **Velocity Stability:** Velocity variance \u003C20% sprint-to-sprint\n- **Scope Change:** \u003C10% scope change after sprint planning\n- **Completion Rate:** >90% of committed stories completed per sprint\n\n**Stakeholder Value:**\n- **Value Delivery:** Every sprint delivers demonstrable user value\n- **Cycle Time:** Average story cycle time \u003C5 days\n- **Lead Time:** Epic to delivery \u003C6 weeks average\n- **Stakeholder Satisfaction:** >4\u002F5 on sprint review feedback\n\n## Related Agents\n\n- [cs-product-manager](cs-product-manager.md) - Full product management lifecycle (RICE, interviews, PRDs)\n- [cs-product-strategist](cs-product-strategist.md) - OKR cascade and strategic planning for roadmap alignment\n- [cs-ux-researcher](cs-ux-researcher.md) - User research to inform story requirements and acceptance criteria\n- Scrum Master - Velocity context and sprint execution (see `..\u002F..\u002Fproject-management\u002Fscrum-master\u002F`)\n\n## References\n\n- **Primary Skill:** [..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002FSKILL.md](..\u002F..\u002Fproduct-team\u002Fagile-product-owner\u002FSKILL.md)\n- **RICE Framework:** [..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002FSKILL.md](..\u002F..\u002Fproduct-team\u002Fproduct-manager-toolkit\u002FSKILL.md)\n- **Product Domain Guide:** [..\u002F..\u002Fproduct-team\u002FCLAUDE.md](..\u002F..\u002Fproduct-team\u002FCLAUDE.md)\n- **Agent Development Guide:** [..\u002FCLAUDE.md](..\u002FCLAUDE.md)\n- **Scrum Master Skill:** [..\u002F..\u002Fproject-management\u002Fscrum-master\u002FSKILL.md](..\u002F..\u002Fproject-management\u002Fscrum-master\u002FSKILL.md)\n\n---\n\n**Last Updated:** March 9, 2026\n**Status:** Production Ready\n**Version:** 1.0\n",{"name":5,"model":23,"tools":24,"domain":30,"skills":31,"description":7},"sonnet",[25,26,27,28,29],"Read","Write","Bash","Grep","Glob","product","product-team\u002Fagile-product-owner, product-team\u002Fproduct-manager-toolkit","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcs-agile-product-owner",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add agisota\u002Fold-one --skill cs-agile-product-owner",{"tool":47,"command":48},"bunx","bunx skills add agisota\u002Fold-one --skill cs-agile-product-owner",{"tool":50,"command":51},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill cs-agile-product-owner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcs-agile-product-owner\u002FSKILL.md",true,[],[56,63,70,79,86,93],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":74,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]