PM-OS — Your AI
Product Partner
Turn your AI coding assistant into a dedicated product partner that knows your product, users, strategy, and competitive position. It compounds over time.
Create your own private copy of PM-OS using the GitHub template. This gives you a clean starting point that you own and control.
Use this templategit clone https://github.com/agentmart/pm-os.git
cd pm-os
Navigate to your PM-OS folder and start Claude Code:
cd pm-os
claude
What happens automatically:
Slash commands available:
/discover /strategy /write-prd /roadmap /competitive /north-star /plg-audit /interview-prep /launch-plan /retro /stakeholder-update /growth-experiment /setup-routine /log-decision /review-prd
No extra configuration needed. Claude Code reads everything automatically from the file structure.
Open your PM-OS folder in VS Code with GitHub Copilot enabled:
cd pm-os
code .
What happens automatically:
How to use skills and commands:
Copilot doesn't have native slash commands, but you can type the same trigger words as natural language in Copilot Chat (Agent Mode). For example, type "write a PRD for [feature]" or "run competitive analysis on [competitor]" and Copilot will follow the routing in CLAUDE.md to load the right skill file.
Reference context files with @workspace:
Use @workspace in Copilot Chat to reference context-library files. For example: "@workspace read context-library/product.md and suggest roadmap priorities."
No extensions or plugins required beyond GitHub Copilot itself.
This is the highest-leverage 30 minutes you'll spend. The better your context, the smarter PM-OS becomes. Open each file in context-library/ and fill in your actual product context.
Each file has guidance comments explaining what to fill and why it matters. Out of the box they are placeholders — filling them in is what turns the template into your PM-OS.
Run this prompt to confirm everything is working. Copy it, paste it into your AI tool, and check the response:
A good response should:
If the response feels generic, go back to Step 3 and add more detail to your context files. PM-OS is only as sharp as the context you give it.
| Category | Includes | Triggered by |
|---|---|---|
| Discovery | Opportunity Solution Tree, User Interviews | discovery research |
| Strategy | Product Strategy Canvas | strategy vision |
| Execution | PRD Writing, Roadmapping, Stakeholder Comms | PRD roadmap |
| Growth | North Star, PLG Strategy, Launch Planning | growth launch |
| Research | Competitive Research | competitor market |
| Design | Product Design Review | design UX |
| Automation | Routine Setup | routine automate |
| Agent | What they critique |
|---|---|
| Engineer | Feasibility, tech debt, implementation risk |
| Designer | UX quality, design system, user flow gaps |
| Executive | Strategic alignment, business impact, board-readiness |
| User Researcher | Evidence quality, assumption risk, user empathy |
| Data Analyst | Metric validity, measurement plan, statistical rigor |
| Legal/Privacy | Compliance risk, data handling, regulatory flags |
| Competitor Watcher | Competitive gaps, differentiation, market timing |
| Monitor | What they do |
|---|---|
| Metrics Tracker | Flags metric anomalies and trend shifts, suggests investigations |
| Assumption Validator | Tracks open assumptions, designs validation experiments |
| Decision Logger | Captures decisions with rationale and counter-arguments |
| Context Updater | Detects stale context-library entries, prompts updates |
| Risk Monitor | Scans for dependency risks, blockers, and emerging threats |
| Template | Use for |
|---|---|
| PRD Template | New feature or initiative briefs |
| Experiment Template | A/B tests and growth experiments |
| Decision Template | Product decision records with rationale |
| Routine Template | Custom PM automation routines |
| Routine | Suggested schedule |
|---|---|
| Weekly Metrics Digest | Monday 8am |
| Competitive Pulse | Monday 9am |
| Backlog Grooming | Weeknights 10pm |
| Stakeholder Update Draft | Friday 3pm |
| Sprint Retro Prep | Bi-weekly |
| User Feedback Synthesis | Wednesday 10am |