Free & Open Source · Built for PMs

Claude Code,
built for Product Managers.

A free operating system for Product Managers using Claude Code. One setup. Your product, your users, your standards — baked in. Every output already calibrated to you.

Clone on GitHub — it's free See how it works →

Skills

Sub-agents

Setup time

< 5 min

Price

Free

Why this exists

AI is only as good as
the context you give it.

Most PMs use Claude like a search engine — paste a question, get a generic answer, spend an hour fixing it. PM OS changes the starting point.

Without PM OS

With PM OS

PRD

"Write a PRD for a bulk export feature." → Claude produces a generic 6-section doc with made-up metrics, no customer evidence, and a success metric of 'increased engagement'.

/prd-writerasks who has the problem, what evidence you have, and what stage you're at. Output: hypothesis-driven, evidence-backed, with real baselines — ready to share with your team.

User stories

"Write user stories for the settings page." → A list of vague, untestable stories with no acceptance criteria and no connection to user value.

/user-storiesdecomposes your brief into INVEST-compliant stories with Given/When/Then criteria. Optionally posts them directly to your GitHub repo.

Leadership report

You write the same Friday update from scratch every week. It takes 30 minutes, sounds slightly different each time, and buries the ask at the bottom.

/leadership-reportstructures it in 2 minutes: status, wins with outcomes, risks with impact, next week, and a specific ask — calibrated to your audience.

Customer docs

"Write a help article for our bulk upload feature." → Marketing-speak, wrong terminology, steps that don't match your actual UI, and no mention of limitations.

/customer-docsknows your product's terminology and UI language. Output: functional, direct, correctly structured — ready for your Help Center.

Marketing brief

"Write a marketing brief for our new AI feature." → Generic positioning, feature-first language, no competitive framing, and personas that fit every B2B SaaS product ever made.

/marketing-briefleads with customer pain, names your actual competitors, and gives your marketing team 3 ready-to-use positioning statements and objection responses.

Customer feedback

You have 8 interview transcripts, a Notion doc of notes, and a meeting this afternoon. You skim them and wing the synthesis. Important signals get lost.

/user-research/interview-summary structures each transcript with key moments and exact quotes. synthesizes them all into ranked findings with confidence levels.

What's inside

Three layers that work together

Not a chatbot wrapper. A structured system built on how PMs actually work.

⚡

13 Skills

Slash commands for every core PM workflow — PRDs, user stories, roadmaps, exec presentations, competitor analysis, and more. Each skill asks the right questions first and produces structured, stage-appropriate output.

🧠

8 Sub-agents

Expert review personas on demand. Say "review as Engineer" and Claude flags missing edge cases. "Review as CPO" and it challenges whether you're solving the right problem at all.

🗂️

Context system

One CLAUDE.md and a context/ library where you define your product, users, terminology, competitors, and existing docs. Set it up once. Every skill uses it forever.

Get started

First value in under 5 minutes

No coding required. Read the official Claude Code quickstart →

1

Install Claude Code & log in

Open your terminal and run:

curl -fsSL https://claude.ai/install.sh | bash

Then authenticate:

claude

2

Clone the repo and open in Cursor

git clone https://github.com/derderiansevan/sevans-product-os.git
cd sevans-product-os
cursor .

3

Fill in your context

Open CLAUDE.md and fill in every [FILL IN] field. The more specific you are, the better every skill performs.

# PM Context
Role:         Senior PM at Acme Corp
Product:      B2B SaaS for procurement teams
Target users: Legal Ops Managers, mid-market
OKRs:         NRR 115% / churn <8%
Terminology:  "workspace" not "project"

4

Run your first skill

In Cursor's chat panel, type a slash command:

/prd-writer

Claude asks 2–3 clarifying questions, then generates a full PRD — hypothesis-driven, stage-appropriate, with a built-in checklist.

5

Get expert review

After generating any document:

Review this as an Engineer and a Skeptic.

Claude adopts each persona and flags specific blockers, risks, and gaps.

Skills

Thirteen workflows, ready to run

Each skill is a slash command. Trigger it, answer 2–3 questions, get structured output calibrated to your context.

PRD Writer/prd-writer

From one-line speclet to full solution review. Adapts to your stage — Team Kickoff, Planning Review, Launch Readiness. Includes hypothesis, problem evidence, success metrics with baselines, non-goals, and rollout plan.

User Stories/user-stories

INVEST-compliant user stories with Given/When/Then acceptance criteria. Handles a single feature or decomposes a full product brief into a batch. Optionally posts directly to any GitHub repo.

Marketing Brief/marketing-brief

Structured briefs for your marketing team: pain statement with customer voice, solution explanation, personas, capabilities, competitive positioning, objection handling, and key numbers.

Interview Prep/interview-prep

Discussion guides for user research sessions. Warm-up → core topic exploration → hypothesis challenge → wrap-up. Includes open-ended questions designed to surface the unexpected, not confirm what you already believe.

Interview Summary/interview-summary

Structured transcript summary: TL;DR, Said vs. Did table, key moments with exact quotes, surprises, and product implications. Captures signals you'd miss when skimming.

User Research/user-research

Synthesizes multiple interview transcripts into structured findings ranked by evidence strength. Distinguishes what participants said vs. did. Includes confidence levels and prioritized product implications.

Competition Analysis/competition-analysis

Evidence-based competitor profiles: what they built, three smart decisions, three gaps, and a table of implications (copy / avoid / differentiate). Uses real data — not opinions.

Customer Docs/customer-docs

Customer-facing Help Center articles. Functional, direct, no marketing language. Covers feature explanations, step-by-step guides, and limitation callouts. Adapts length to topic complexity.

Leadership Report/leadership-report

Structured Slack updates for leadership and stakeholders. Format: status, wins, risks/blockers, next week's focus, asks. Skimmable, outcome-focused, and calibrated to your audience.

Roadmap/roadmap

RICE and ICE scoring for your initiative list. Outputs Now/Next/Later format with a narrative for each horizon. Three versions: internal team, executive, and customer-facing. Requires a Not Doing list.

Release Notes/release-notes

Three formats from one input: customer-facing (benefit-led), internal/team (technical detail), and public changelog. Works from a PRD, feature list, or GitHub diff. No feature-first language.

Exec Presentation/exec-presentation

Slide narrative architecture for QBRs, board updates, roadmap reviews, and launch readiness. Outputs a slide-by-slide structure with talking points — so you stay in control of the story.

Internal Slides/internal-slides

Slide decks for team audiences — sprint reviews, planning kickoffs, design reviews, retrospectives, and cross-functional syncs. Built for discussion, not just approval. Includes speaker notes and timed discussion prompts.

Sub-agents