Turn scattered notes, chat logs, meeting fragments, issue updates, or calendar context into a concise daily brief. Use when Codex needs to summarize what hap...
Coding
daily-standup-notes
Try itGenerate structured daily standup notes from a free-form brain dump. Use when the user wants to turn scattered thoughts into a clean 3-section standup update (Yesterday / Today / Blockers), or asks for "standup notes", "daily update", "what did I do yesterday", or "scrum update".
What it does
Generate structured daily standup notes from a free-form brain dump. Use when the user wants to turn scattered thoughts into a clean 3-section standup update (Yesterday / Today / Blockers), or asks for "standup notes", "daily update", "what did I do yesterday", or "scrum update".
The skill document
Daily Standup Notes
Turn a free-form brain dump into a clean, scannable standup update in three sections:
- Yesterday — completed work
- Today — planned work
- Blockers — anything blocking progress
Quick start
- Read the user's raw input (chat, bullet list, voice transcript, etc.).
- Classify each item into one of the three buckets.
- Output a concise markdown list under each heading.
- If a bucket is empty, write "None reported."
Formatting rules
- Use past tense for Yesterday items, present/future tense for Today items.
- Merge duplicate or near-duplicate items.
- Keep each bullet to one line; split long items into sub-bullets.
- Preserve names, PR numbers, ticket IDs, and links verbatim.
- If an item is ambiguous (could be Yesterday or Today), place it in Today and prefix with "[continue]".
Output template
**Yesterday**
- ...
**Today**
- ...
**Blockers**
- ...
Tips
- Offer to save the output to a dated file (e.g.
standup/2025-01-15.md) when the user doesn't specify a destination. - For recurring use, suggest appending to a weekly rollup file.
Related skills
Turn raw meeting notes or transcripts into structured action: decisions log, action items with owner and deadline, open questions, and a distributable summary email. Extracts who-committed-to-what with date parsing (natural language dates resolved against the meeting date), deduplicates, tracks carryover between meetings, and generates per-owner task lists. Use when the user has meeting notes/transcripts and needs minutes, action items, or a follow-up summary.
Extract key ideas and turn a chat into a polished visual summary card
Generate a 1-on-1 brief from GitHub activity. Fully deterministic pipeline — 5 tool calls, zero sub-agent spawns.
Create and organize daily work notes with consistent structure, date-based filenames, and lightweight summaries. Use when the user wants to start a daily log, append structured entries to today's note, review recent notes, or generate a concise recap from multiple daily files.
Generate evidence-based project weekly reports from a local code repository. Use when the user asks for a project weekly report, weekly update, status summar...