Product Owner Advisor
Ongoing product owner judgment: sprint goals, backlog health, saying no mid-sprint, velocity forecasts as date ranges, and story acceptance.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you write user stories for mobile checkout. User stories typically follow the format 'As a user, I want to do something, so that some benefit happens.' You'd want to break down the checkout flow into individual stories. For each one, you'd have acceptance criteria that define when it's complete. You might also estimate story points if you use that. Think about the different user types and what actions they need to take. Do you have a design for the checkout flow? What payment methods do you want to support?
USER STORY 1: Guest checkout As a first-time buyer, I want to complete checkout without creating an account, so I can purchase without friction. Acceptance Criteria: • Email field pre-filled if available from email list • Password creation step skipped entirely • Confirmation email sent (includes order number, shipping, total) • Session guest_id linked to order, persists across refresh • Estimated Story Points: 5 • Acceptance Test: Guest buys on mobile, receives confirmation in 10s • Dependencies: Payment gateway integration (Story 4) USER STORY 2: Payment method selection As a mobile buyer, I want to choose Apple Pay, Google Pay, or card entry, so I complete payment with my preferred method. Acceptance Criteria: • Apple Pay button visible only on iOS with valid payment method • Google Pay button visible only on Android with saved card • Card entry form fallback for all browsers • Each method attempts in priority order on form submit • Estimated Story Points: 8 • Acceptance Test: Apple Pay payment on iPhone 15 completes in 3 taps • Bugs to watch: iOS 17 edge cases, Android 14 Google Pay timeout USER STORY 3: Shipping address entry As a buyer on mobile, I want to enter my address with autocomplete, so I don't mistype and shipping arrives. Acceptance Criteria: • Autocomplete via Google Places API (free tier, 100K requests/day) • Phone number field auto-formatted (+1-555-1234) • Address validation against USPS before checkout proceeds • "Use billing address" toggle to skip re-entry • Estimated Story Points: 5 • Bugs: Autocomplete flakiness on slow networks (< 2G); fallback plain input SPRINT PRIORITY: 1-2-3 (Ship payment → then shipping → then guest) VELOCITY: 18 points/sprint target; scope to 3 stories if team capacity shows <18
About this skill
The product owner calls you make every week, made with a veteran's rules: what goes next, what gets refused, what done means, and which date to promise. Works from your real backlog, velocity, and stakeholders, not Scrum theory.
What it does
- Rewrites sprint goals into one outcome the team can still hit if stories drop
- Diagnoses backlog health: size, age, items that trace to no goal, and who really decides order
- Drafts replies to stakeholders and mid-sprint requests that name the trade-off and a landing date
- Forecasts release dates as a range from your last 5-8 sprints, with a scope-growth allowance
- Applies Definition of Done and acceptance criteria to accept or reject work, with no partial credit
What you get
A short answer for quick calls, a single piece (sprint goal, forecast, stakeholder reply) when that is all you need, or a diagnosis and 30-day plan when you are new to the role or resetting it.
Best for
New or overloaded product owners, founders acting as PO, and team leads who keep getting asked for dates.
SKILL.md preview
---
name: agile-product-owner
description: Act as an experienced Scrum/agile product owner across the whole role - product goal and sprint goals, backlog ordering and health, saying no to stakeholders, mid-sprint change requests, release forecasts from velocity as ranges, Definition of Done, and accepting or rejecting work at sprint review. Use when the user says "I'm the new PO, where do I start?", "a VP wants this in the current sprint", "when will this epic ship?", "our backlog has 400 items", "should I accept this story?", "how do I say no to sales", or "is our sprint goal any good?".
---
# Agile Product Owner
… (sign up to view the full skill)More business & ops skills
View all Business & Ops skills →Product Practice Diagnostic
Trace a product-team symptom (unused features, roadmap churn, priority fights) to the broken stage of the loop and fix one thing first.
Feature Launch Go-to-Market Plan
Plan one feature launch: tier, plan access, audience messages, readiness gates for support, sales, billing, and docs, and success metrics.
Pricing Tier and Packaging Diagnosis
Finds why your pricing tiers underperform and redesigns value metric, fences, price gaps, and upgrade triggers with a migration plan.
Product Specs, Roadmaps, and Research Decisions
Turn customer evidence into testable PRDs, dependency-aware roadmaps, and stakeholder updates with clear decisions and tradeoffs.