Menu
Use when drafting the weekly stakeholder update. Run after weekly-summary is complete.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding a new data source to the daily summary — MCP tools, CLI commands, local file paths, or HTTP endpoints. Triggered by "add source", "/add-source", "add to my daily summary", or "connect [tool] to my daily summary".
Use when drafting the end-of-day summary. Reads today's meetings, Slack, and memory files to append a structured summary to today's daily note.
Use when setting up pm-ground-control for the first time. Creates the workspace folder structure, populates memory files through an interview, and installs skills.
Use when preparing for a job search, updating a resume, prepping for interviews, or doing a performance review. Triggered by "review accomplishments", "/accomplishments-review", "prepare for interviews", "update my resume", "performance review prep".
Use when capturing a specific accomplishment for job searching, performance reviews, or interview prep. Triggered by "log accomplishment", "/log-accomplishment", "add to my accomplishments", or "remember this for my resume".
Use when synthesizing the week's daily notes into a weekly summary document. Run at end of week.
| name | weekly-update |
| description | Use when drafting the weekly stakeholder update. Run after weekly-summary is complete. |
Draft a stakeholder-facing weekly update from the weekly summary. Format is configured in memory/me.md.
Read memory/me.md for:
Find this week's weekly summary. Look for {{WORKSPACE}}/daily-notes/YYYY/WW/YYYY-WW.md. If it doesn't exist, prompt: "Weekly summary not found. Run /weekly-summary first, then come back."
Read the summary in full.
Write a stakeholder-facing update from the weekly summary. This is external-facing — write for the audience, not as internal notes.
Tone and style:
Structure (adapt to format):
**Week of [Mon date]–[Fri date]**
**Summary**
[2-3 sentences: what the week added up to, the most important thing that happened]
**[Project Name]**
[1-3 bullets: what moved, what was decided, where it stands]
**[Project Name]**
[1-3 bullets]
**Looking ahead**
[2-3 bullets: what's on deck next week, any upcoming decisions or milestones]
Omit projects with no activity. Do not include the internal to-do list. Do not include "What I drove" verbatim — fold the most important items into the project summaries where they add context.
Apply the format from memory/me.md:
Slack post:
*bold*, _italic_, bullet points with -Email:
Weekly update — week of [Mon date]Notion page:
Weekly Update — Week of [Mon date]Other: Follow whatever format the user specified in setup.
Present the draft to the user. Ask: "Does this look right, or would you like any changes?"
If the user approves:
slack_send_message to the appropriate channel or DM (ask for confirmation of destination)gmail_create_draft (ask for recipient)"Weekly update drafted for week of [Mon date]–[Fri date]. [Sent to / Saved as draft for / Copied to clipboard for] [destination]."