agile-product-ownerAgile 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.
Install via ClawdBot CLI:
clawdbot install alirezarezvani/agile-product-ownerBacklog management and sprint execution toolkit for product owners, including user story generation, acceptance criteria patterns, sprint planning, and velocity tracking.
Create INVEST-compliant user stories from requirements:
As a [persona],
I want to [action/capability],
So that [benefit/value].Example:
As a marketing manager,
I want to export campaign reports to PDF,
So that I can share results with stakeholders who don't have system access.| Type | Template | Example |
|------|----------|---------|
| Feature | As a [persona], I want to [action] so that [benefit] | As a user, I want to filter search results so that I find items faster |
| Improvement | As a [persona], I need [capability] to [goal] | As a user, I need faster page loads to complete tasks without frustration |
| Bug Fix | As a [persona], I expect [behavior] when [condition] | As a user, I expect my cart to persist when I refresh the page |
| Enabler | As a developer, I need to [technical task] to enable [capability] | As a developer, I need to implement caching to enable instant search |
| Persona | Typical Needs | Context |
|---------|--------------|---------|
| End User | Efficiency, simplicity, reliability | Daily feature usage |
| Administrator | Control, visibility, security | System management |
| Power User | Automation, customization, shortcuts | Expert workflows |
| New User | Guidance, learning, safety | Onboarding |
Write testable acceptance criteria using Given-When-Then format.
Given [precondition/context],
When [action/trigger],
Then [expected outcome].Examples:
Given the user is logged in with valid credentials,
When they click the "Export" button,
Then a PDF download starts within 2 seconds.
Given the user has entered an invalid email format,
When they submit the registration form,
Then an inline error message displays "Please enter a valid email address."
Given the shopping cart contains items,
When the user refreshes the browser,
Then the cart contents remain unchanged.Each story should include criteria for:
| Category | Example |
|----------|---------|
| Happy Path | Given valid input, When submitted, Then success message displayed |
| Validation | Should reject input when required field is empty |
| Error Handling | Must show user-friendly message when API fails |
| Performance | Should complete operation within 2 seconds |
| Accessibility | Must be navigable via keyboard only |
| Story Points | Minimum AC Count |
|--------------|------------------|
| 1-2 | 3-4 criteria |
| 3-5 | 4-6 criteria |
| 8 | 5-8 criteria |
| 13+ | Split the story |
See references/user-story-templates.md for complete template library.
Break epics into deliverable sprint-sized stories:
| Technique | When to Use | Example |
|-----------|-------------|---------|
| By workflow step | Linear process | "Checkout" ā "Add to cart" + "Enter payment" + "Confirm order" |
| By persona | Multiple user types | "Dashboard" ā "Admin dashboard" + "User dashboard" |
| By data type | Multiple inputs | "Import" ā "Import CSV" + "Import Excel" |
| By operation | CRUD functionality | "Manage users" ā "Create" + "Edit" + "Delete" |
| Happy path first | Risk reduction | "Feature" ā "Basic flow" + "Error handling" + "Edge cases" |
Epic: User Dashboard
Breakdown:
Epic: User Dashboard (34 points total)
āāā US-001: View key metrics (5 pts) - End User
āāā US-002: Customize layout (5 pts) - Power User
āāā US-003: Export data to CSV (3 pts) - End User
āāā US-004: Share with team (5 pts) - End User
āāā US-005: Set up alerts (5 pts) - Power User
āāā US-006: Filter by date range (3 pts) - End User
āāā US-007: Admin overview (5 pts) - Admin
āāā US-008: Enable caching (3 pts) - EnablerPlan sprint capacity and select stories:
Sprint Capacity = Average Velocity Ć Availability Factor
Example:
Average Velocity: 30 points
Team availability: 90% (one member partially out)
Adjusted Capacity: 27 points
Committed: 23 points (85% of 27)
Stretch: 4 points (15% of 27)| Scenario | Factor |
|----------|--------|
| Full sprint, no PTO | 1.0 |
| One team member out 50% | 0.9 |
| Holiday during sprint | 0.8 |
| Multiple members out | 0.7 |
Sprint Capacity: 27 points
Sprint Goal: [Clear, measurable objective]
COMMITTED (23 points):
[H] US-001: User dashboard (5 pts)
[H] US-002: Export feature (3 pts)
[H] US-003: Search filter (5 pts)
[M] US-004: Settings page (5 pts)
[M] US-005: Help tooltips (3 pts)
[L] US-006: Theme options (2 pts)
STRETCH (4 points):
[L] US-007: Sort options (2 pts)
[L] US-008: Print view (2 pts)See references/sprint-planning-guide.md for complete planning procedures.
Prioritize backlog using value and effort assessment.
| Priority | Definition | Sprint Target |
|----------|------------|---------------|
| Critical | Blocking users, security, data loss | Immediate |
| High | Core functionality, key user needs | This sprint |
| Medium | Improvements, enhancements | Next 2-3 sprints |
| Low | Nice-to-have, minor improvements | Backlog |
| Factor | Weight | Questions |
|--------|--------|-----------|
| Business Value | 40% | Revenue impact? User demand? Strategic alignment? |
| User Impact | 30% | How many users? How frequently used? |
| Risk/Dependencies | 15% | Technical risk? External dependencies? |
| Effort | 15% | Size? Complexity? Uncertainty? |
Before adding to sprint, validate each story:
| Criterion | Question | Pass If... |
|-----------|----------|------------|
| Independent | Can this be developed without other uncommitted stories? | No blocking dependencies |
| Negotiable | Is the implementation flexible? | Multiple approaches possible |
| Valuable | Does this deliver user or business value? | Clear benefit in "so that" |
| Estimable | Can the team estimate this? | Understood well enough to size |
| Small | Can this complete in one sprint? | ā¤8 story points |
| Testable | Can we verify this is done? | Clear acceptance criteria |
references/user-story-templates.md contains:
references/sprint-planning-guide.md contains:
# Generate stories from sample epic
python scripts/user_story_generator.py
# Plan sprint with capacity
python scripts/user_story_generator.py sprint 30Generates:
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
ā TestableTrack sprint health and team performance.
| Metric | Formula | Target |
|--------|---------|--------|
| Velocity | Points completed / sprint | Stable Ā±10% |
| Commitment Reliability | Completed / Committed | >85% |
| Scope Change | Points added or removed mid-sprint | <10% |
| Carryover | Points not completed | <15% |
Sprint 1: 25 points
Sprint 2: 28 points
Sprint 3: 30 points
Sprint 4: 32 points
Sprint 5: 29 points
------------------------
Average Velocity: 28.8 points
Trend: Stable
Planning: Commit to 24-26 pointsStory is complete when:
Generated Mar 1, 2026
A product owner for an online retail platform uses the skill to write user stories for new features like one-click checkout and personalized recommendations. They create acceptance criteria using Given-When-Then for testing and prioritize backlog items based on customer feedback to plan sprints effectively.
In a software-as-a-service company, the product owner applies the skill to break down epics like a new analytics dashboard into sprint-sized stories. They estimate story points using Fibonacci scale, track velocity to forecast delivery, and ensure stories meet INVEST criteria for incremental value.
A product owner in a healthcare organization uses the skill to generate user stories for patient portal enhancements, such as appointment scheduling. They define acceptance criteria for validation and error handling, plan sprints based on regulatory deadlines, and prioritize backlog to meet compliance needs.
For a financial technology startup, the product owner leverages the skill to write user stories for features like fraud detection alerts. They create acceptance criteria with performance benchmarks, estimate story points for sprint capacity, and prioritize backlog items to align with quarterly business goals.
In an edtech company, the product owner uses the skill to break down an epic for a new learning module into deliverable stories. They apply splitting techniques by workflow steps, validate stories against INVEST criteria, and plan sprints to ensure timely release for academic terms.
This model involves recurring revenue from monthly or annual subscriptions for software access. The skill helps product owners prioritize features that reduce churn and increase user engagement, using sprint planning to deliver updates regularly and maintain competitive advantage.
Revenue is generated from sales commissions or direct product transactions. The skill assists product owners in writing user stories for checkout optimizations and inventory management, estimating story points to plan sprints that boost conversion rates and operational efficiency.
This model offers a free basic service with paid upgrades for advanced features. The skill enables product owners to break down epics for premium capabilities, create acceptance criteria to ensure quality, and prioritize backlog to drive upsell conversions through targeted sprint deliveries.
š¬ Integration Tip
Integrate this skill with project management tools like Jira or Trello by using its templates for user stories and acceptance criteria to streamline backlog updates. Align sprint planning outputs with team velocity data for accurate forecasting.
Create jobs and transact with other specialised agents through the Agent Commerce Protocol (ACP) ā extends the agent's action space by discovering and using agents on the marketplace, enables launching an agent token for fundraising and revenue, and supports registering service offerings to sell capabilities to other agents.
Write, structure, and update a business plan for a solopreneur. Use when creating a plan from scratch, updating an existing plan after a pivot or new phase, or preparing a plan to share with investors, partners, or even just to clarify your own strategy. Covers executive summary, market analysis, competitive positioning, revenue model, operations plan, financial projections, and risk assessment ā all adapted for a one-person business. Trigger on "write a business plan", "business plan", "create my plan", "business plan template", "update my business plan", "plan for my business", "investor pitch plan".
Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.
Strategic product leadership toolkit for Head of Product including OKR cascade generation, market analysis, vision setting, and team scaling. Use for strategic planning, goal alignment, competitive analysis, and organizational design.
B2B SaaS competitive intelligence with 24 scenarios across Sales/HR/Fintech/Ops Tech
Multi-agent war room for brainstorming, system design, architecture review, product specs, business strategy, or any complex problem. Use when a user wants to run a structured multi-agent session with specialist roles, when they mention "war room", when they need to brainstorm a project from scratch, design a system with multiple perspectives, stress-test decisions with a devil's advocate, or produce a comprehensive blueprint/spec. Works for software, hardware, content, business ā any domain.