agile-product-owner
by alirezarezvaniagile-product-owner is a Scrum Product Management skill for user stories, acceptance criteria, epic breakdowns, sprint planning, backlog prioritization, and velocity-aware capacity notes.
This skill scores 80/100, making it a solid listing candidate for directory users who want an agent to support Scrum product-owner work. The repository provides clear triggers, substantial workflow guidance, templates, references, and a supporting script, so it should help an agent execute with less guesswork than a generic prompt. Users should mainly note its Scrum-specific scope and the lack of visible install instructions in the provided evidence.
- Strong triggerability: frontmatter lists concrete intents such as writing user stories, creating acceptance criteria, sprint planning, backlog grooming, INVEST criteria, and velocity tracking.
- Operational content is substantive: SKILL.md is large and organized around story generation, acceptance criteria, epic breakdown, sprint planning, prioritization, references, and tools.
- Reusable artifacts increase agent leverage, including user story and sprint planning templates, sprint planning and user story reference guides, and a Python user story generator.
- Scope is explicitly Scrum/product-owner oriented and excludes Kanban-only, waterfall, and scaled agile frameworks without adaptation.
- Repository evidence does not show a README or install command in SKILL.md, so adoption relies on directory tooling or manual path discovery.
Overview of agile-product-owner skill
What the agile-product-owner skill is for
The agile-product-owner skill is a Scrum-oriented product management skill for turning product intent into usable backlog artifacts: user stories, acceptance criteria, epic breakdowns, sprint plans, backlog priorities, and velocity-aware planning notes. It is best for product owners, product managers, scrum masters, delivery leads, and founders who need structured backlog output rather than a generic brainstorming response.
Best-fit Product Management workflows
Use the agile-product-owner skill when you are preparing backlog refinement, writing stories from a feature idea, checking whether a story is INVEST-ready, planning a sprint around team capacity, or converting an epic into smaller implementation slices. It is especially useful for teams that already use Scrum language such as sprint goal, story points, Definition of Done, velocity, dependencies, and Given/When/Then acceptance criteria.
What makes it different from a normal prompt
The skill adds a product-owner operating model instead of only producing story text. The source materials include reusable story and sprint planning templates, guidance for capacity calculation, prioritization, sprint ceremonies, acceptance criteria patterns, and common story anti-patterns. The included scripts/user_story_generator.py also shows the intended structure for INVEST-style user story generation across personas and story types.
Important fit limits before installing
This is not a general project management skill. The upstream metadata explicitly marks it as a poor fit for Kanban-only workflows, waterfall project planning, general task management, or scaled agile frameworks such as SAFe and LeSS unless you adapt the language and process. If your team does not estimate, plan sprints, or maintain a prioritized backlog, the output may feel heavier than necessary.
How to Use agile-product-owner skill
agile-product-owner install and repository reading path
Install the skill in a compatible Claude skills setup with:
npx skills add alirezarezvani/claude-skills --skill agile-product-owner
After install, read SKILL.md first to understand triggers and workflows. Then open assets/user_story_template.md for the expected story format, assets/sprint_planning_template.md for sprint planning fields, references/user-story-templates.md for INVEST and acceptance criteria patterns, and references/sprint-planning-guide.md for capacity, planning agenda, and validation checklists. Review scripts/user_story_generator.py if you want to understand or customize the persona/story-type logic.
Inputs that produce better agile-product-owner usage
The skill works best when you provide product context, not just a feature name. Include the target persona, user problem, business goal, known constraints, dependencies, non-goals, priority, expected release window, and any engineering or design notes. For sprint planning, add sprint length, team members’ availability, historical velocity, carryover work, must-have commitments, and risks.
Weak input: “Write stories for reporting.”
Stronger input: “Use agile-product-owner to break down an epic for exporting campaign reports. Persona: marketing manager. Goal: share PDF results with executives who do not use the app. Include happy path, permission edge cases, export failure handling, out-of-scope items, dependencies on analytics API, and story point assumptions for a 2-week Scrum sprint.”
Suggested workflow for stories, epics, and sprints
For a new feature, start by asking for an epic breakdown before requesting final stories. Then have the skill validate each candidate story against INVEST, add Given/When/Then acceptance criteria, identify dependencies, and separate out-of-scope items. For sprint planning, ask it to compare planned points against adjusted capacity rather than simply filling the sprint with top-priority items.
A practical flow is: define epic goal → split by user value → draft stories → add acceptance criteria → check Definition of Done → estimate or flag estimation assumptions → prioritize → select sprint candidates → produce risks and dependency table.
Prompt pattern for reliable results
Use an instruction that names the artifact you want and the decision you need to make. Example:
“Use the agile-product-owner skill to prepare backlog refinement for this feature. Output: 1 epic summary, 6–10 user stories, acceptance criteria in Given/When/Then format, INVEST concerns, dependencies, suggested priority, and questions for engineering. Optimize for a B2B SaaS admin workflow and keep compliance logging in scope.”
This style gives the skill enough boundaries to avoid vague stories and enough context to produce backlog-ready work.
agile-product-owner skill FAQ
Is agile-product-owner for Product Management beginners?
Yes, if you are learning Scrum product ownership and need templates for user stories, acceptance criteria, sprint planning, and backlog grooming. Beginners should still review the generated output with engineering and design because estimates, dependencies, and Definition of Done items require team-specific judgment.
When should I not use this skill?
Do not use it as-is for Kanban-only delivery, waterfall schedules, generic personal task lists, or organizations that do not work in sprints. It can still provide story-writing help, but the sprint capacity and velocity guidance may create unnecessary process overhead.
How does it compare with asking ChatGPT or Claude directly?
A direct prompt can write a user story, but the agile-product-owner skill gives the agent a consistent Scrum product-owner frame: story templates, acceptance criteria patterns, epic breakdown workflow, prioritization concepts, capacity planning, and sprint documentation. That consistency matters when you need repeatable backlog quality across many features.
Does it replace Jira, Linear, or Azure DevOps?
No. The skill helps create and refine the content that goes into tools such as Jira, Linear, Azure DevOps, or GitHub Issues. It does not manage the source of truth, enforce workflow states, calculate real velocity from your tracker, or replace team planning conversations.
How to Improve agile-product-owner skill
Improve agile-product-owner outputs with richer context
The fastest way to improve agile-product-owner results is to provide real constraints: personas, workflow screenshots or descriptions, platform limits, API dependencies, analytics goals, legal/compliance requirements, and what is explicitly out of scope. The skill can structure ambiguity, but it cannot infer your roadmap tradeoffs or team capacity accurately without data.
Watch for common failure modes
Common issues include stories that are too broad, acceptance criteria that restate the story instead of testing behavior, missing edge cases, hidden technical dependencies, and sprint plans that ignore holidays, support rotation, or unfinished carryover work. Ask the skill to flag assumptions and unresolved questions rather than presenting every item as ready.
Iterate after the first draft
After the first output, run a refinement pass: “Find stories that violate INVEST,” “split anything larger than 8 points,” “add negative scenarios,” “identify dependencies by team,” or “convert these into Jira-ready tickets.” For sprint plans, ask for a risk-adjusted version using reduced capacity and a separate stretch-goal list.
Customize the skill for your team’s process
If you adopt the skill heavily, adapt the templates to your Definition of Ready, Definition of Done, estimation scale, priority model, and ticket fields. The most useful customization targets are assets/user_story_template.md, assets/sprint_planning_template.md, and the persona/story-type assumptions in scripts/user_story_generator.py. This keeps the agile-product-owner skill aligned with your actual Product Management workflow instead of a generic Scrum template.