Help us improve
Share bugs, ideas, or general feedback.
From execution-skills
Synthesizes Slack mentions, Google Calendar events, and Google Drive documents modified in the last 7 days into a personal PM weekly brief. Use Fridays for decisions, blockers, shipped items, and deadlines recap.
npx claudepluginhub amplitude/builder-skills --plugin execution-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/execution-skills:pm-weekly-briefThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**A personal week-in-review written for you — decisions, risks, wins, and what's coming next.**
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
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.
Structures a PM's weekly review and planning session, producing a shareable update covering metrics, shipping progress, blockers, insights, and next week's top 3 priorities.
Share bugs, ideas, or general feedback.
A personal week-in-review written for you — decisions, risks, wins, and what's coming next.
By Friday you've had 30 meetings, 200 Slack messages, and a handful of docs updated. This skill reads your Slack mentions, calendar, and Drive activity to produce a clean weekly brief.
/schedule
Read for activity from the last 7 days:
- My Slack mentions and DMs
- My Google Calendar events (attended and upcoming)
- Google Drive documents modified in the last 7 days
## Week of {{WEEK_DATE_RANGE}}
### Key Decisions
Decisions made this week from meetings, Slack, or docs. One sentence each.
If discussed but not decided, put in Open Questions.
### Risks & Blockers
Anything that slowed progress or is unresolved. Include owner and what's needed to unblock.
### Important Conversations
2–4 bullets of recurring themes or significant exchanges — signal only.
### Shipped
Features, experiments, or changes that went live. Link to ticket or doc if available.
### Upcoming Deadlines
Meetings, launches, or deliverables in the next 7–14 days.
Rules:
- Keep the whole brief under 400 words
- Lead each section with the most important item
- If a section has nothing to report, write "Nothing notable this week"
- Save to {{OUTPUT_FOLDER}} as PM-Brief-YYYY-MM-DD.md
- Return the Drive link when done
| Field | Value |
|---|---|
| MCPs required | Slack, Google Calendar, Google Drive |
| Output | PM-Brief-YYYY-MM-DD.md → /Product/Weekly briefs |
| Scheduler | Weekly, Friday afternoon |
{{WEEK_DATE_RANGE}} — Auto-populated by the scheduler{{OUTPUT_FOLDER}} — e.g. /Product/Weekly briefsstakeholder-update to turn this into a polished leadership update.