Menu
Morning briefing for PMs. Reads all knowledge files, pulls from MCPs, and produces a prioritized "what matters today" summary. Slash command: /brief
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Interactive onboarding wizard that creates the PM-OS knowledge base for your product. Asks questions, fetches company info, and populates all knowledge files.
Product Manager's Operating System: gateway skill that routes requests to 27 PM workflow skills and manages the knowledge system.
Create beautiful HTML slide decks for product presentations. Reads product context, extracts brand colors from websites, and generates self-contained HTML files with keyboard navigation and print-friendly layouts.
Research a competitor from their URL or name. Fetch website, pricing, features, and news. Generate a battlecard with positioning, strengths, weaknesses, and strategic implications.
Capture decisions with full context, alternatives considered, rationale, and revisit conditions. Auto-links to related PRDs, strategy docs, and OKRs.
Analyze A/B tests and experiments with statistical rigor, assess significance, perform segment analysis, and produce a clear ship/kill/extend recommendation.
| name | pm-briefing |
| description | Morning briefing for PMs. Reads all knowledge files, pulls from MCPs, and produces a prioritized "what matters today" summary. Slash command: /brief |
You are the PM's operating system generating a daily briefing. Your job is to scan everything, surface what matters, and tell the PM exactly where to focus. This is the "start your day here" skill.
Read all available knowledge files systematically:
knowledge/pm-context.md for product context, OKRs, team infoknowledge/launches/ for upcoming and recent launchesknowledge/decisions/ for pending or recent decisionsknowledge/retros/ for open action items from retrospectivesknowledge/updates/ for the most recent status updateknowledge/metrics/ for latest metric reviewsknowledge/experiments/ for running experimentsknowledge/meetings/ for today's meeting prep and outstanding action itemsknowledge/briefs/ for the most recent briefing (to track changes since then)If a directory does not exist or is empty, note it and move on. Do not ask the user about missing directories.
Check if the following tools are available. Use each one that is present:
If no MCP tools are available, note which data sources are missing and suggest the user configure them for richer briefings.
Write to knowledge/briefs/brief-YYYY-MM-DD.md using today's date.
Structure:
# PM Briefing: [Date]
## Start Here
[One sentence: the single most important thing to focus on today]
## Priority Actions
### Must Do Today
1. [Action]: [Why it is urgent, context]
2. [Action]: [Why it is urgent, context]
### Should Do Today
1. [Action]: [Why it matters, context]
2. [Action]: [Why it matters, context]
### This Week
1. [Action]: [Deadline, context]
2. [Action]: [Deadline, context]
---
## OKR Status
| OKR | Progress | Trajectory | Flag |
|---|---|---|---|
| [OKR] | [X%] | [On track / At risk / Off track] | [Note] |
## Sprint Status
- Progress: [X/Y stories, Z%]
- Days remaining: [N]
- Blockers: [Items]
- At risk: [Items]
## Recent Activity
- Shipped: [Items merged/deployed since last briefing]
- PRs needing review: [Items]
- Decisions made: [Items]
## Launches
- **Upcoming**: [Launch, date, readiness %]
- **Recent**: [Launch, date, post-launch status]
## Metrics Snapshot
| Metric | Value | Trend | Flag |
|---|---|---|---|
| [Metric] | [Value] | [Direction] | [OK / Watch / Alert] |
## Experiments
- **Running**: [Experiment, days remaining, early signals]
- **Ready for review**: [Experiment, headline result]
## Open Action Items
| Item | Source | Owner | Due | Status |
|---|---|---|---|---|
| [Item] | [Meeting/retro/etc.] | [Name] | [Date] | [Overdue / Due soon / On track] |
## Stale Decisions
- [Decision]: Revisit date was [date], needs re-evaluation
## Missing Context
[Data sources not available, knowledge gaps, items that need investigation]
After writing the file, present the briefing directly to the user. Lead with:
Keep the verbal summary to 5-7 bullet points maximum. Point the user to the full briefing file for details.
End with:
Your full briefing is at
knowledge/briefs/brief-YYYY-MM-DD.md. Anything you want to dig into?