Frameworks for building and scaling product operations functions across growing teams.
Works with
Bridges product and operations by creating systems that enable PMs to focus on strategy rather than operational overhead like release management, enablement, and cross-functional coordination
Standardizes processes, tooling, and insights across product teams while preserving PM decision-making authority; product ops informs, not decides
Addresses common scaling challenges: surfacing user research a
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionproduct-operationsExecute the skills CLI command in your project's root directory to begin installation:
Fetches product-operations from refoundai/lenny-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate product-operations. Access via /product-operations in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
616
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
616
stars
Help the user build and scale product operations functions using frameworks from 5 product leaders.
When the user asks for help with product operations:
Brian Tolkin: "One solution to that problem, our solution at the time was to start up a new function called product operations who had accountability and reported into operations but physically sat with and operated much like a member of the product team." Product ops originated as a bridge between centralized product teams and distributed operations, ensuring product decisions account for operational reality.
Christine Itwaru: "Product operations for a VP or a head of product or a product manager is the creation of some system that allows you to thrive or allows your team to thrive in product management." The function is about building systems that enable product management, not doing product management itself.
Geoff Charles: "We invested early on in product operations... they basically are tasked with a lot of the work that needs to get done to continue shipping products and scaling product development." Product ops handles release management, enablement, and operational tasks that would otherwise distract PMs from their core work.
Melissa Perri + Denise Tilles: "Product operations does not take away decision making rights from the product manager. It's there to inform them." Product ops provides insights and infrastructure but doesn't make product decisions - that remains with PMs.
Melissa Perri: "Product management at scale is really hard, and that's where product operations comes in. So what it does is it helps you get the right insights to the team, and then help standardize those outputs and those check-ins." The function focuses on standardizing roadmaps, scaling user research, and surfacing data insights across the organization.
For all 5 insights from 5 guests, see references/guest-insights.md
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
product-operations is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in product-operations — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in product-operations — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend product-operations for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: product-operations is focused, and the summary matches what you get after install.
product-operations fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added product-operations from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for product-operations matched our evaluation — installs cleanly and behaves as described in the markdown.
product-operations is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
product-operations reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 25