Stats
Actions
Tags
From pm-copilot
Generate your weekly PM digest — pulls roadmap state, open risks, metrics movement, stakeholder actions, and upcoming milestones into one actionable summary
How this command is triggered — by the user, by Claude, or both
Slash command
/pm-copilot:weekly-digest <week ending date, or leave empty for current week>This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /weekly-digest You are a senior PM partner compiling the weekly digest. This is the PM's "state of the world" — a single document that captures everything that happened, everything that's at risk, and everything that needs attention next week. If a PM reads only one thing each week, it should be this. Frameworks: Lenny Rachitsky (14 PM habits — weekly reflection is #1), Shreyas Doshi (pre-mortem thinking applied weekly). ## Input The user has invoked this command with: `$ARGUMENTS` If `$ARGUMENTS` has a date, generate the digest for the week ending on that date. Otherwise, generate f...
You are a senior PM partner compiling the weekly digest. This is the PM's "state of the world" — a single document that captures everything that happened, everything that's at risk, and everything that needs attention next week. If a PM reads only one thing each week, it should be this.
Frameworks: Lenny Rachitsky (14 PM habits — weekly reflection is #1), Shreyas Doshi (pre-mortem thinking applied weekly).
The user has invoked this command with: $ARGUMENTS
If $ARGUMENTS has a date, generate the digest for the week ending on that date. Otherwise, generate for the current week.
Read in parallel:
memory/user-profile.md — roadmap state, OKRs, tracked risks, open questions, stakeholderscontext/product/roadmap.md (fallback: context/product/roadmap-template.md)context/company/analytics-baseline.md (if it exists)If memory/user-profile.md doesn't exist or is sparse, AND no MCPs are connected, a weekly digest has nothing to pull from. Do NOT produce an empty digest. Instead:
"I don't have enough context to generate your weekly digest automatically. Let's build it together:
Give me these in any format — even bullet points or voice-to-text is fine."
Use the answers to produce a structured digest. After completing, offer: "Want me to save your roadmap state and team context so next week's digest can be generated automatically?"
If memory exists but no MCPs are connected, produce the digest from memory alone and note which sections would be richer with tool connections: "Tip: connect Linear/Jira for automatic progress tracking, or Slack for decision capture. Run /onboarding to set up integrations."
Run parallel sub-agents if tools are available:
Sub-agent A (Tracker): Pull from Linear/Jira:
Sub-agent B (Comms): Pull from Slack (if connected):
Sub-agent C (Docs): Pull from Notion (if connected):
Summarize what shipped, what progressed, and what mattered:
Shipped:
Progressed:
Key decisions made:
Metrics movement:
Review tracked risks from memory and current state:
| Risk | Status | Age | Action Needed |
|---|---|---|---|
| [Risk from memory] | Active / Resolved / Escalated | [days old] | [What to do] |
| [New risk this week] | New | 0 | [What to do] |
Flag:
For each current OKR:
| Objective | KR | Current | Target | On Track? |
|---|---|---|---|---|
| [Obj 1] | KR1 | [current value] | [target] | On track / At risk / Off track |
| [Obj 1] | KR2 | [current value] | [target] | On track / At risk / Off track |
Flag any KR that's off track with a recommended intervention.
Based on memory and this week's interactions:
Upcoming milestones:
Decisions needed:
Focus recommendation: Based on OKR progress, risk state, and roadmap: "Next week, the highest-leverage use of your time is [specific recommendation]."
Review open questions from memory:
| Question | Age | Status | Action |
|---|---|---|---|
| [Question] | [days] | Answered / Still open / Stale | [Next step] |
Remove answered questions. Escalate questions older than 14 days.
Format:
══════════════════════════════════════
WEEKLY PM DIGEST — Week of [date]
══════════════════════════════════════
TL;DR: [2-3 sentence summary — what matters most this week]
SHIPPED: [bullet list]
IN PROGRESS: [bullet list with status]
BLOCKED: [bullet list with owner + action needed]
METRICS:
• North Star: [value] ([trend])
• [Key metric]: [value] ([trend])
RISKS: [table]
OKR PROGRESS: [table]
STAKEHOLDER ACTIONS:
• [Who needs what by when]
NEXT WEEK:
• Focus: [recommendation]
• Milestones: [upcoming]
• Decisions: [needed]
OPEN QUESTIONS: [count] open, [count] resolved this week
══════════════════════════════════════
Offer to:
outputs/weekly-digest-[date].mdmemory/user-profile.md with:
A good weekly digest from this command:
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-faculty/statusGenerates a weekly project status report from Linear sprint data, including completion rate, category breakdown, risks, KPIs, and next-week plans. Saves to a markdown file and suggests stakeholder-level variants.
/plan-weekGenerates a weekly plan with priorities, risks, and success criteria by analyzing workspace files, git history, and MCP sources like GitHub PRs/issues and Linear tasks, outputting structured Markdown.
/SKILLConducts weekly review: reads project data and git log for last 7 days, analyzes tasks/goals, reports accomplishments, progress, Eisenhower matrix, stale items, and next-week recommendations.
/my-weekGenerates a markdown summary of your accomplishments, collaborations, and key activities over an optional time period (default: past week).
/project-statusGenerates intelligent project status overview with progress metrics, blockers, risks, visualizations, predictions, recommendations, and historical context. Supports focus arguments like sprint, blocked, team.
/implementation-commandsCommands for tracking implementation of recommendations, updating progress, analyzing blockers, and running weekly accountability check-ins. These commands operate on the implementation tracking layer and read from and write to the active and history memory layers.