Product Ops Skills for AI Agents

31 open-source skills for the work that keeps product teams running: launches, customer feedback, metrics, planning, decisions, and docs. Built for product ops, product managers, and anyone who ends up owning "how we work." Works with Claude Code, the Claude app, OpenAI Codex, Cursor, and any agent that supports the Agent Skills spec.

Browse every skill at charlenetstrain.github.io/product-ops-skills.

Built by Charlene Strain. Sibling library: Product Marketing Ops Skills.

Contributions welcome. Have a better way to run one of these, or a skill to add? Open a PR or request a skill.

Contents

• What are skills?
• How the skills work together
• The rules every skill follows
• All skills
• Install
• Use
• Contributing

What are skills?

A skill is a markdown file of instructions an AI agent follows for one specific job. Add these to your setup, and when you paste in meeting notes, a ticket export, or a roadmap, the agent recognizes the job and does it the same way every time.

How the skills work together

Everything starts with product-ops-context. Run it once and it writes .agents/product-ops-context.md: your product, your teams and who decides what, your meeting rhythm, where things live, and what each metric means. Every other skill reads that file first, so it only asks you for what's specific to the task.

                       ┌──────────────────────────────────────┐
                       │          product-ops-context         │
                       │    (read by every other skill first) │
                       └───────────────────┬──────────────────┘
                                           │
     ┌─────────────┬─────────────┬─────────┴───┬─────────────┬─────────────┐
     ▼             ▼             ▼             ▼             ▼             ▼
┌───────────┐┌───────────┐┌───────────┐┌───────────┐┌───────────┐┌───────────┐
│ Launches  ││ Feedback  ││ Metrics   ││ Planning  ││ Decisions ││ Knowledge │
│ & releases││ & requests││ & data    ││ & roadmap ││ & owners  ││ & tools   │
├───────────┤├───────────┤├───────────┤├───────────┤├───────────┤├───────────┤
│readiness  ││intake     ││definitions││quarterly  ││decision   ││SOPs       │
│enablement ││duplicates ││kpi-health ││roadmap    ││  log      ││info debt  │
│release    ││tagging    ││experiments││  hygiene  ││meeting →  ││onboarding │
│  notes    ││VoC digest ││data       ││dependency ││  actions  ││tool audit │
│sprint     ││escalations││  requests ││  map      ││RACI       ││vendor     │
│  review   ││CAB prep   ││           ││pricing log││retros     ││  scorecard│
│beta       ││           ││           ││           ││ritual     ││           │
│flags      ││           ││           ││           ││  calendar ││           │
│deprecation││           ││           ││           ││           ││           │
└───────────┘└───────────┘└───────────┘└───────────┘└───────────┘└───────────┘

Skills hand off to each other. A few chains that come up most:

• Feedback tagging → Voice of customer digest: tag raw feedback, then summarize it for leadership
• Request intake triage → Duplicate request merging: sort new asks, then merge them into the backlog with accurate counts
• Product metrics definitions → KPI health check: agree on what each number means, then check how it's moving
• Launch readiness checklist → Internal enablement brief → Release notes drafting: confirm it's ready, brief the field, tell customers
• Meeting to action converter → Decision log: capture actions from a meeting, and log the decisions in full

Each skill ends with a Related skills section naming what it hands off to and why.

The rules every skill follows

• Every open item gets one named owner. "Marketing" isn't an owner.
• "We discussed it" and "we decided it" stay separate.
• Nothing gets invented. If the notes don't say why, the output says "Not recorded."
• Skills recommend. People decide.

All skills

Start here

Skill	What it does
Product ops context	Writes down your product, teams, owners, meetings, tools, and metrics once, so every other skill can read it

Launches and releases

Getting changes out the door, and making sure every team knows before customers do.

Skill	What it does
Launch readiness checklist	Runs a cross-functional go / no-go check with an owner on every gap
Internal enablement brief	One page for sales, support, and success before customers hear about a change
Release notes drafting	Turns tickets and changelogs into customer-facing release notes
Sprint review summary	Translates what engineering shipped into what it means for everyone else
Beta program manager	Beta plans with exit criteria set up front, tracking, and a go-live readout
Feature flag tracking	A plain-words register of what's on, for whom, and when it comes out
Deprecation plan	Retires a feature with a timeline, customer messages, and a plan for stragglers

Customer feedback and requests

Turning what customers say and ask for into something the team can count and act on.

This is the beginning of the README. Read the rest at the original. Read the full README ↗