From pm-copilot
Use this skill when the user asks to "write my weekly update", "weekly PM digest", "weekly report", "write my status update", "end of week summary", "weekly standup summary", "write the PM weekly", "update the team this week", or needs to produce a regular cadence update covering what shipped, what's in progress, and what's next.
npx claudepluginhub productfculty-aipm/pm-copilot-by-product-facultyThis skill uses the workspace's default tool permissions.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
You are writing the weekly PM update — a regular cadence communication that keeps the team, leadership, and stakeholders aligned on product progress without requiring a meeting.
Framework: Lenny's 14 PM habits (clarity above all), Pyramid Principle (organize by insight, not chronology).
Read memory/user-profile.md for: roadmap state (Now/Next/Later), OKRs, stakeholders who receive the weekly update, and communication preferences. If Linear/Jira MCP is connected, pull current sprint state.
Extract from memory and any input the user provides:
Shipped: What was completed and deployed this week? (Pull from Linear/Jira "done" if connected)
In progress: What's actively being worked on? Any changes to status or ETA?
Metrics: What moved this week? What's the trend vs. target?
Decisions made: Any significant decisions this week (prioritization, scope changes, approach decisions)?
Blockers: Any blockers that need to be surfaced to leadership?
What you learned: Any customer conversations, data signals, or team observations worth sharing?
Next week's focus: Top 3 priorities for the coming week.
If the user hasn't provided all of this, ask for the gaps or infer from memory.
Use the context/templates/weekly-report-template.md structure. Apply the Pyramid Principle:
Tone calibration:
For the metrics table, pull from:
context/company/analytics-baseline.md for baseline valuesIf no current metrics are available, leave placeholders and note: "Update before sending — these are empty."
After writing the digest:
open_questions in memory older than 7 days that should be surfaced?tracked_risks in memory that need to be mentioned?Produce the weekly digest using the template. Offer to:
outputs/weekly-[date].mdmemory/user-profile.md with any new items surfaced during this session