Agile Product Owner
Generate sprint planning docs with goals, capacity, story selection, and dependency tracking for indie teams running lightweight Scrum.
Overview
Agile Product Owner is an agent skill most often used in Build (also Validate) that produces a full sprint planning document with capacity, velocity, stories, and dependencies.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill agile-product-ownerWhat is this skill?
- Structured sprint info table (dates, goal, Scrum Master, Product Owner)
- Team capacity matrix with person-days and velocity vs planned points
- Selected stories table with points, assignee, MoSCoW priority, status
- Dependencies section with blocking stories, owners, due dates
- Expandable sprint goal narrative defining done for the sprint
Adoption & trust: 798 installs on skills.sh; 17.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a backlog but no single sprint doc that ties goal, capacity, committed stories, and blockers together before the team starts.
Who is it for?
Solo founders or two-person teams running sprints who want a consistent planning artifact without buying full PM software.
Skip if: Teams that only need a one-off feature spec with no recurring sprint cadence, or orgs already standardized on Jira sprint views with no markdown export need.
When should I use this skill?
User needs sprint planning, product owner ceremony docs, or a sprint goal with capacity and story tables.
What do I get? / Deliverables
You get a filled sprint planning template ready to share with stakeholders and developers for the iteration kickoff.
- Sprint planning markdown document
- Capacity and velocity summary
- Dependency register for the sprint
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Sprint planning is the canonical shelf for ongoing delivery cadence after scope is set—where backlog turns into a time-boxed commitment. Product-owner and sprint ceremonies live under build/pm because they govern what ships in the next iteration, not one-off research.
Where it fits
Break a validated MVP into sprint-sized stories with points before full build.
Run sprint planning with capacity adjusted for PTO and on-call.
Plan a release sprint with dependencies on external API readiness.
How it compares
Use instead of improvising sprint notes in chat—it's a planning template, not an analytics or roadmap MCP.
Common Questions / FAQ
Who is agile-product-owner for?
Indie builders, technical founders, and small squads acting as their own product owner who need structured sprint planning output from an agent.
When should I use agile-product-owner?
At the start of each sprint in build/pm to lock goal and scope; in validate/scope when turning a prototype plan into story-pointed work; before ship/launch when aligning a release sprint with a hard date.
Is agile-product-owner safe to install?
Review the Security Audits panel on this Prism page before installing; the skill is document-generation only and does not require network or secrets by default.
SKILL.md
READMESKILL.md - Agile Product Owner
# Sprint Planning Document ## Sprint Info | Field | Value | |-------|-------| | **Sprint** | Sprint [Number] | | **Dates** | [Start Date] - [End Date] | | **Sprint Goal** | [One sentence describing what this sprint achieves] | | **Scrum Master** | [Name] | | **Product Owner** | [Name] | --- ## Sprint Goal [Expand on the sprint goal. What is the single most important outcome? What does "done" look like for this sprint? 2-3 sentences.] --- ## Team Capacity | Team Member | Available Days | Notes | |------------|---------------|-------| | [Name] | [X] / [Total] | [PTO, training, on-call, etc.] | | [Name] | [X] / [Total] | | | [Name] | [X] / [Total] | | **Total Capacity:** [X] person-days **Historical Velocity:** [X] story points (avg of last 3 sprints) **Planned Velocity:** [X] story points (adjusted for capacity) --- ## Selected Stories | # | Story | Points | Assignee | Priority | Status | |---|-------|--------|----------|----------|--------| | 1 | [Story title with ticket link] | [SP] | [Name] | Must Have | To Do | | 2 | [Story title with ticket link] | [SP] | [Name] | Must Have | To Do | | 3 | [Story title with ticket link] | [SP] | [Name] | Should Have | To Do | | 4 | [Story title with ticket link] | [SP] | [Name] | Nice to Have | To Do | **Total Planned:** [X] story points --- ## Dependencies | Dependency | Blocking Story | Owner | Status | Due Date | |-----------|---------------|-------|--------|----------| | [External API ready] | [Story #] | [Name/Team] | [Status] | [Date] | | [Design review complete] | [Story #] | [Name] | [Status] | [Date] | --- ## Risks | Risk | Impact | Likelihood | Mitigation | |------|--------|-----------|-----------| | [Risk description] | High/Med/Low | High/Med/Low | [Plan] | | [Risk description] | High/Med/Low | High/Med/Low | [Plan] | --- ## Definition of Done - [ ] Code complete and peer reviewed - [ ] Unit tests written and passing - [ ] Acceptance criteria verified - [ ] Documentation updated (if applicable) - [ ] Deployed to staging environment - [ ] QA sign-off received - [ ] Product Owner acceptance --- ## Sprint Ceremonies | Ceremony | Day/Time | Duration | |----------|----------|----------| | Daily Standup | [Day] [Time] | 15 min | | Sprint Review | [Date] [Time] | 60 min | | Sprint Retrospective | [Date] [Time] | 60 min | # User Story ## Story Info | Field | Value | |-------|-------| | **Title** | [Short descriptive title] | | **Epic** | [Parent epic name/link] | | **Story Points** | [Estimate] | | **Priority** | Must Have / Should Have / Nice to Have | | **Assignee** | [Name] | | **Sprint** | [Sprint number] | --- ## User Story **As a** [type of user/role], **I want** [capability or feature], **So that** [benefit or value I receive]. --- ## Acceptance Criteria ### Scenario 1: [Happy Path] - **Given** [precondition or context] - **When** [action the user takes] - **Then** [expected outcome] ### Scenario 2: [Alternative Path] - **Given** [precondition or context] - **When** [action the user takes] - **Then** [expected outcome] ### Scenario 3: [Edge Case / Error] - **Given** [precondition or context] - **When** [action the user takes] - **Then** [expected error handling or outcome] --- ## Notes - [Technical notes, design references, API details] - [Dependencies on other stories or external systems] - [Out of scope items for this story] - [Links to mockups, prototypes, or design files] --- ## Definition of Done - [ ] Acceptance criteria met - [ ] Code reviewed and approved - [ ] Tests written and passing - [ ] Documentation updated - [ ] Product Owner accepted # Sprint Planning Guide Sprint planning workflows, capacity calculation, and backlog management. --- ## Table of Contents - [Sprint Planning Workflow](#sprint-planning-workflow) - [Capacity Planning](#capacity-planning) - [Backlog Prioritization](#backlog-prioritization) - [Sprint Ceremonies](#sprint-ceremonies) - [Metrics and Tracking](#metrics-and-tracking) --- ## Sprint Planning