# Send Agile Product Owner to your agent Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually. ## Fast path - Download the package from Yavira. - Extract it into a folder your agent can access. - Paste one of the prompts below and point your agent at the extracted folder. ## Suggested prompts ### New install ```text I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete. ``` ### Upgrade existing ```text I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run. ``` ## Machine-readable fields ```json { "schemaVersion": "1.0", "item": { "slug": "agile-product-owner", "name": "Agile Product Owner", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/alirezarezvani/agile-product-owner", "canonicalUrl": "https://clawhub.ai/alirezarezvani/agile-product-owner", "targetPlatform": "OpenClaw" }, "install": { "downloadUrl": "/downloads/agile-product-owner", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=agile-product-owner", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "packageFormat": "ZIP package", "primaryDoc": "SKILL.md", "includedAssets": [ "SKILL.md", "references/sprint-planning-guide.md", "references/user-story-templates.md", "scripts/user_story_generator.py" ], "downloadMode": "redirect", "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-04-23T16:43:11.935Z", "expiresAt": "2026-04-30T16:43:11.935Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=4claw-imageboard", "contentDisposition": "attachment; filename=\"4claw-imageboard-1.0.1.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/agile-product-owner" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] } }, "links": { "detailUrl": "https://openagent3.xyz/skills/agile-product-owner", "downloadUrl": "https://openagent3.xyz/downloads/agile-product-owner", "agentUrl": "https://openagent3.xyz/skills/agile-product-owner/agent", "manifestUrl": "https://openagent3.xyz/skills/agile-product-owner/agent.json", "briefUrl": "https://openagent3.xyz/skills/agile-product-owner/agent.md" } } ``` ## Documentation ### Agile Product Owner Backlog management and sprint execution toolkit for product owners, including user story generation, acceptance criteria patterns, sprint planning, and velocity tracking. ### Table of Contents User Story Generation Workflow Acceptance Criteria Patterns Epic Breakdown Workflow Sprint Planning Workflow Backlog Prioritization Reference Documentation Tools ### User Story Generation Workflow Create INVEST-compliant user stories from requirements: Identify the persona (who benefits from this feature) Define the action or capability needed Articulate the benefit or value delivered Write acceptance criteria using Given-When-Then Estimate story points using Fibonacci scale Validate against INVEST criteria Add to backlog with priority Validation: Story passes all INVEST criteria; acceptance criteria are testable ### User Story Template As a [persona], I want to [action/capability], So that [benefit/value]. Example: As a marketing manager, I want to export campaign reports to PDF, So that I can share results with stakeholders who don't have system access. ### Story Types TypeTemplateExampleFeatureAs a [persona], I want to [action] so that [benefit]As a user, I want to filter search results so that I find items fasterImprovementAs a [persona], I need [capability] to [goal]As a user, I need faster page loads to complete tasks without frustrationBug FixAs a [persona], I expect [behavior] when [condition]As a user, I expect my cart to persist when I refresh the pageEnablerAs a developer, I need to [technical task] to enable [capability]As a developer, I need to implement caching to enable instant search ### Persona Reference PersonaTypical NeedsContextEnd UserEfficiency, simplicity, reliabilityDaily feature usageAdministratorControl, visibility, securitySystem managementPower UserAutomation, customization, shortcutsExpert workflowsNew UserGuidance, learning, safetyOnboarding ### Acceptance Criteria Patterns Write testable acceptance criteria using Given-When-Then format. ### Given-When-Then Template Given [precondition/context], When [action/trigger], Then [expected outcome]. Examples: Given the user is logged in with valid credentials, When they click the "Export" button, Then a PDF download starts within 2 seconds. Given the user has entered an invalid email format, When they submit the registration form, Then an inline error message displays "Please enter a valid email address." Given the shopping cart contains items, When the user refreshes the browser, Then the cart contents remain unchanged. ### Acceptance Criteria Checklist Each story should include criteria for: CategoryExampleHappy PathGiven valid input, When submitted, Then success message displayedValidationShould reject input when required field is emptyError HandlingMust show user-friendly message when API failsPerformanceShould complete operation within 2 secondsAccessibilityMust be navigable via keyboard only ### Minimum Criteria by Story Size Story PointsMinimum AC Count1-23-4 criteria3-54-6 criteria85-8 criteria13+Split the story See references/user-story-templates.md for complete template library. ### Epic Breakdown Workflow Break epics into deliverable sprint-sized stories: Define epic scope and success criteria Identify all personas affected by the epic List all capabilities needed for each persona Group capabilities into logical stories Validate each story is ≤8 points Identify dependencies between stories Sequence stories for incremental delivery Validation: Each story delivers standalone value; total stories cover epic scope ### Splitting Techniques TechniqueWhen to UseExampleBy workflow stepLinear process"Checkout" → "Add to cart" + "Enter payment" + "Confirm order"By personaMultiple user types"Dashboard" → "Admin dashboard" + "User dashboard"By data typeMultiple inputs"Import" → "Import CSV" + "Import Excel"By operationCRUD functionality"Manage users" → "Create" + "Edit" + "Delete"Happy path firstRisk reduction"Feature" → "Basic flow" + "Error handling" + "Edge cases" ### Epic Example Epic: User Dashboard Breakdown: Epic: User Dashboard (34 points total) ├── US-001: View key metrics (5 pts) - End User ├── US-002: Customize layout (5 pts) - Power User ├── US-003: Export data to CSV (3 pts) - End User ├── US-004: Share with team (5 pts) - End User ├── US-005: Set up alerts (5 pts) - Power User ├── US-006: Filter by date range (3 pts) - End User ├── US-007: Admin overview (5 pts) - Admin └── US-008: Enable caching (3 pts) - Enabler ### Sprint Planning Workflow Plan sprint capacity and select stories: Calculate team capacity (velocity × availability) Review sprint goal with stakeholders Select stories from prioritized backlog Fill to 80-85% of capacity (committed) Add stretch goals (10-15% additional) Identify dependencies and risks Break complex stories into tasks Validation: Committed points ≤85% capacity; all stories have acceptance criteria ### Capacity Calculation Sprint Capacity = Average Velocity × Availability Factor Example: Average Velocity: 30 points Team availability: 90% (one member partially out) Adjusted Capacity: 27 points Committed: 23 points (85% of 27) Stretch: 4 points (15% of 27) ### Availability Factors ScenarioFactorFull sprint, no PTO1.0One team member out 50%0.9Holiday during sprint0.8Multiple members out0.7 ### Sprint Loading Template Sprint Capacity: 27 points Sprint Goal: [Clear, measurable objective] COMMITTED (23 points): [H] US-001: User dashboard (5 pts) [H] US-002: Export feature (3 pts) [H] US-003: Search filter (5 pts) [M] US-004: Settings page (5 pts) [M] US-005: Help tooltips (3 pts) [L] US-006: Theme options (2 pts) STRETCH (4 points): [L] US-007: Sort options (2 pts) [L] US-008: Print view (2 pts) See references/sprint-planning-guide.md for complete planning procedures. ### Backlog Prioritization Prioritize backlog using value and effort assessment. ### Priority Levels PriorityDefinitionSprint TargetCriticalBlocking users, security, data lossImmediateHighCore functionality, key user needsThis sprintMediumImprovements, enhancementsNext 2-3 sprintsLowNice-to-have, minor improvementsBacklog ### Prioritization Factors FactorWeightQuestionsBusiness Value40%Revenue impact? User demand? Strategic alignment?User Impact30%How many users? How frequently used?Risk/Dependencies15%Technical risk? External dependencies?Effort15%Size? Complexity? Uncertainty? ### INVEST Criteria Validation Before adding to sprint, validate each story: CriterionQuestionPass If...IndependentCan this be developed without other uncommitted stories?No blocking dependenciesNegotiableIs the implementation flexible?Multiple approaches possibleValuableDoes this deliver user or business value?Clear benefit in "so that"EstimableCan the team estimate this?Understood well enough to sizeSmallCan this complete in one sprint?≤8 story pointsTestableCan we verify this is done?Clear acceptance criteria ### User Story Templates references/user-story-templates.md contains: Standard story formats by type (feature, improvement, bug fix, enabler) Acceptance criteria patterns (Given-When-Then, Should/Must/Can) INVEST criteria validation checklist Story point estimation guide (Fibonacci scale) Common story antipatterns and fixes Story splitting techniques ### Sprint Planning Guide references/sprint-planning-guide.md contains: Sprint planning meeting agenda Capacity calculation formulas Backlog prioritization framework (WSJF) Sprint ceremony guides (standup, review, retro) Velocity tracking and burndown patterns Definition of Done checklist Sprint metrics and targets ### User Story Generator # Generate stories from sample epic python scripts/user_story_generator.py # Plan sprint with capacity python scripts/user_story_generator.py sprint 30 Generates: INVEST-compliant user stories Given-When-Then acceptance criteria Story point estimates (Fibonacci scale) Priority assignments Sprint loading with committed and stretch items ### Sample Output USER STORY: USR-001 ======================================== Title: View Key Metrics Type: story Priority: HIGH Points: 5 Story: As a End User, I want to view key metrics and KPIs so that I can save time and work more efficiently Acceptance Criteria: 1. Given user has access, When they view key metrics, Then the result is displayed 2. Should validate input before processing 3. Must show clear error message when action fails 4. Should complete within 2 seconds 5. Must be accessible via keyboard navigation INVEST Checklist: ✓ Independent ✓ Negotiable ✓ Valuable ✓ Estimable ✓ Small ✓ Testable ### Sprint Metrics Track sprint health and team performance. ### Key Metrics MetricFormulaTargetVelocityPoints completed / sprintStable ±10%Commitment ReliabilityCompleted / Committed>85%Scope ChangePoints added or removed mid-sprint<10%CarryoverPoints not completed<15% ### Velocity Tracking Sprint 1: 25 points Sprint 2: 28 points Sprint 3: 30 points Sprint 4: 32 points Sprint 5: 29 points ------------------------ Average Velocity: 28.8 points Trend: Stable Planning: Commit to 24-26 points ### Definition of Done Story is complete when: Code complete and peer reviewed Unit tests written and passing Acceptance criteria verified Documentation updated Deployed to staging environment Product Owner accepted No critical bugs remaining ## Trust - Source: tencent - Verification: Indexed source record - Publisher: alirezarezvani - Version: 2.1.1 ## Source health - Status: healthy - Source download looks usable. - Yavira can redirect you to the upstream package for this source. - Health scope: source - Reason: direct_download_ok - Checked at: 2026-04-23T16:43:11.935Z - Expires at: 2026-04-30T16:43:11.935Z - Recommended action: Download for OpenClaw ## Links - [Detail page](https://openagent3.xyz/skills/agile-product-owner) - [Send to Agent page](https://openagent3.xyz/skills/agile-product-owner/agent) - [JSON manifest](https://openagent3.xyz/skills/agile-product-owner/agent.json) - [Markdown brief](https://openagent3.xyz/skills/agile-product-owner/agent.md) - [Download page](https://openagent3.xyz/downloads/agile-product-owner)