Menu
Use when synthesizing the week's daily notes into a weekly summary document. Run at end of week.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
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 drafting the weekly stakeholder update. Run after weekly-summary is complete.
| name | weekly-summary |
| description | Use when synthesizing the week's daily notes into a weekly summary document. Run at end of week. |
Synthesize the week's daily notes into a single weekly summary document and save it to the workspace.
Read memory/me.md for workspace path. Use currentDate from context to identify the current week.
{{WORKSPACE}}/daily-notes/YYYY/WW/YYYY-WW.md (or alongside daily notes — use whatever convention exists, create if new)For each working day this week (Monday through today):
{{WORKSPACE}}/daily-notes/YYYY/MM/YYYY-MM-DD.md### What happened today narrative### What I drove today bullets (if present)### To-dos block — all unchecked - [ ] itemsRead memory/projects.md and memory/me.md for context.
What moved this week: 3-5 sentences. Identify the 2-4 themes that ran across the week — decisions made, problems solved, things shipped, things stuck. Not a day-by-day recap — what the week added up to.
Project sections: One section per active project (from memory/projects.md). For each:
Write "No activity this week." if a project had nothing.
Open to-dos: Collect all unchecked - [ ] items from across the week's daily notes. Deduplicate — if the same item appears across multiple days, keep the most recent version. Apply the same ownership filter as daily-summary: only your own tasks.
Format the same as daily-summary to-dos:
#### Date-anchored
- [ ] [task] — [deadline] 🤖
#### Quick actions
- [ ] [task]
#### Deep work
- [ ] [task] 🤖
#### To-be-triaged
- [ ] [task]
What I drove this week: Collect all "What I drove today" bullets from the week. Deduplicate and consolidate — if the same project or decision appears across multiple days, merge into one bullet. Apply the same high bar: decisions made, documents produced, alignment achieved, PRs shipped, problems solved. Write as 3-7 plain bullets. Omit if nothing clears the bar.
Create or overwrite {{WORKSPACE}}/daily-notes/YYYY/WW/YYYY-WW.md:
### To-dos
#### Date-anchored
...
#### Quick actions
...
#### Deep work
...
#### To-be-triaged
...
## Weekly Summary
### What moved this week
[3-5 sentence narrative]
### [Project Name]
[One sentence: where things stand at end of week.]
- [What moved]
- [Detail]
- Open questions:
- [Question]
### What I drove this week
- [plain bullet]
"Weekly summary written to
[path]. Week of [Mon date]–[Fri date]. [N] open to-dos. [Any notable flags.]"