Agile Product Owner Skill for Smarter Sprint Agents

Where this fits

You're mid-sprint, staring at a backlog that's grown into a jungle of half-formed ideas. The product manager is on leave, and you need to break down an epic into testable stories, estimate points, and prep for tomorrow's sprint planning—all before your next code review. That's exactly the moment you'd normally sink three hours into Jira. Instead, you can hand the grunt work to a Claude agent armed with the agile-product-owner skill, which turns raw notes into structured backlog items and sprint plans.

Why agents benefit

• Generates INVEST-compliant user stories with a consistent template, including roles, goals, and benefits—so you stop rewriting low-quality tickets.
• Produces acceptance criteria in Given-When-Then format directly from story context, reducing ambiguity and back-and-forth with developers.
• Facilitates sprint planning by calculating capacity from historical velocity and team availability, then suggesting a realistic sprint scope.
• Breaks down epics recursively into manageable stories, each with its own story point estimate based on complexity and risk.
• Tracks velocity and sprint progress by analyzing completed points across sprints, prompting adjustments for the next iteration.

Practical scenarios

Backlog Grooming on Autopilot

You paste a messy epic description and a few scattered comments. The agent identifies the underlying user outcomes, splits the epic into 5–7 stories, and drafts acceptance criteria for each. You review and merge—grooming that took an hour now takes ten minutes.

Sprint Planning Under Time Pressure

With two days to go, you need a coherent sprint. The agent pulls your team's historical velocity, checks open capacity, and suggests a prioritized subset of stories. It even flags dependencies and warns if the load exceeds 85% of capacity.

Retrospective That Actually Drives Change

The agent summarizes last sprint's completion rate, highlights stories that slipped, and correlates that with complexity estimates. It then proposes a new estimation guideline for ambiguous tasks—turning retro notes into actionable process tweaks.

Add it to your agent workflow

Install the skill directly from the command line:

npx skills add alirezarezvani/claude-skills --skill agile-product-owner

Then trigger it in Claude with a natural language request like:

Use the agile-product-owner skill: Break down this epic into user stories with acceptance criteria. Here's the epic: "Users should be able to export reports in PDF and Excel."

The skill will output a structured backlog with story points and formatting you can paste straight into your tracker.

Compare before adopting

Before committing, check three things: quality signals (star count, open issues, response quality on real prompts), maintenance freshness (recent commits, README updates), and alternatives—do you already have a custom prompt that works better? Also consider workflow fit: this skill is Scrum-specific, so if your team uses Kanban or SAFe without adaptation, the not_for section signals it won't help.

Why it is worth tracking

With over 25,000 stars, this repository shows strong community momentum and a well-maintained skill ecosystem. The skill's trigger list aligns tightly with daily product owner language, and its structured outputs integrate with common tools like Jira or Linear. Track it because it's not just a one-off script—it's a repeatable capability that keeps your backlog healthy and your sprint ceremonies less painful. You can find more details about its evolution on the skill page, and re-evaluate it whenever you change your agile process.