From pm-os
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.
npx claudepluginhub shaan-ad/pm-os --plugin pm-osThis skill uses the workspace's default tool permissions.
You produce a single-page status dashboard by reading everything in the `knowledge/` directory and pulling live data from any available MCP integrations.
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.
Produces a project-scoped knowledge dashboard with recent entries, corrections, expiring/stale items, and unresolved work. Team mode adds activity, teammate entries, and review queue.
Share bugs, ideas, or general feedback.
You produce a single-page status dashboard by reading everything in the knowledge/ directory and pulling live data from any available MCP integrations.
knowledge/ exists. If not, tell the user: "No knowledge base found. Run /pm-setup first."knowledge/pm-context.md to get product context and preferences.Read all available knowledge files. For each section below, note what data exists and what is missing.
Read these files (skip any that don't exist):
knowledge/pm-context.md : Product contextknowledge/okrs.md : OKR definitions and progressknowledge/team.md : Team infoknowledge/roadmap/*.md : Roadmap itemsknowledge/sprints/*.md : Sprint scoping (look for the most recent)knowledge/decisions/*.md : Recent decisions (last 5)knowledge/launches/*.md : Upcoming or recent launchesknowledge/metrics/*.md : Latest metrics snapshotsknowledge/feedback/synthesis-*.md : Latest feedback synthesisknowledge/priorities/*.md : Current prioritizationknowledge/experiments/*.md : Active experimentsCheck if these tools are accessible. Use them if they are, skip gracefully if not.
Linear / Jira (project management tools):
GitHub (source control):
Slack (communication):
For each integration that is NOT available, add a small note in the dashboard: "(Live data unavailable, install {tool} MCP for real-time updates)"
Present the dashboard in this format:
# Product Dashboard: {product_name}
*Generated: {today's date and time}*
---
## OKR Progress
{For each objective, show the objective and each key result with progress if known}
{If no progress data, show the OKRs and mark "Progress: not yet tracked"}
| Objective | Key Result | Status |
|-----------|-----------|--------|
| {obj} | {kr} | {status or "Not tracked"} |
---
## Sprint Status
{Current sprint name/number if known}
{Ticket counts by status: To Do, In Progress, Done}
{Blocked items highlighted}
{If no sprint data: "No sprint data. Run /sprint-scope to plan your next sprint."}
---
## Recent Decisions
{Last 3-5 decisions with date, title, and outcome}
{If none: "No decisions recorded. Use /decision-record after your next key decision."}
---
## Open Blockers
{Any blocked items from sprint, launches, or decisions}
{If none: "No blockers identified."}
---
## Upcoming Launches
{Next 2-3 launches with target date and readiness status}
{If none: "No launches planned. Use /launch when you're ready."}
---
## Metrics Snapshot
{Latest values for key metrics from pm-context.md}
{Trends if multiple snapshots exist}
{If no data: "No metrics recorded. Use /metrics-check to start tracking."}
---
## Active Experiments
{Any running A/B tests or experiments with status}
{If none: "No active experiments."}
---
## Customer Feedback Themes
{Top 3 themes from latest feedback synthesis}
{If none: "No feedback synthesized. Use /feedback-synthesis to analyze customer feedback."}
---
## What Needs Attention
{Synthesize: what looks off, what's overdue, what's at risk}
{Specific recommendations with skill commands to resolve each}
pm-context.md.