From pm-os
Generates prioritized daily briefing for PMs: scans knowledge files (OKRs, launches, decisions, metrics, actions) and MCPs (Linear/Jira sprints, GitHub PRs/issues, Slack comms). /brief slash command.
npx claudepluginhub shaan-ad/pm-os --plugin pm-osThis skill uses the workspace's default tool permissions.
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.
Generates a single-page markdown product status dashboard from knowledge files and MCP integrations like GitHub, Jira, Linear, showing OKR progress, sprint status, decisions, blockers, launches, and metrics.
Generates personalized status briefings from GitHub PRs/issues/commits, emails, Teams/Slack, synthesizing updates in user's style for defined audiences like team or leadership.
Generates async standup notes from Git commit history, Jira tickets, Obsidian vaults, and calendars for remote team coordination and visibility.
Share bugs, ideas, or general feedback.
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?