Created
May 18, 2026 17:18
-
-
Save pejmanjohn/c217ff879238ab545d6ffea038d166ce to your computer and use it in GitHub Desktop.
Codex-granola-weekly-automation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Every Monday at 8:00 a.m., review all of my [@granola](plugin://granola@openai-curated) call transcripts from the prior calendar week. Create an Automation for this and its output should append to this thread. | |
| Your job is to identify the most important things I need to do, monitor more closely, or think about more deeply based on those conversations. | |
| Organize the output as a weekly review with these sections: | |
| 1. Executive Summary | |
| - The 3–5 most important takeaways from the week. | |
| - Highlight anything urgent, high-leverage, or easy to miss. | |
| 2. Action Items | |
| - List concrete tasks I need to do. | |
| - Include owner, deadline, related person/company/project, and transcript context when available. | |
| - Separate confirmed commitments from inferred follow-ups. | |
| 3. Things to Monitor More Closely | |
| - Risks, open loops, metrics, people issues, customer signals, product concerns, or operational details that may need more attention. | |
| - Explain why each item matters. | |
| 4. Topics to Think About More Deeply | |
| - Strategic questions, product decisions, team dynamics, business tradeoffs, or recurring themes that deserve reflection. | |
| - Frame these as thoughtful prompts or questions, not just summaries. | |
| 5. Follow-ups I May Owe People | |
| - Identify people I may need to respond to, check in with, update, or schedule time with. | |
| - Include context and suggested next step. | |
| 6. Patterns Across Conversations | |
| - Identify recurring themes, repeated concerns, contradictions, or opportunities that appeared in multiple calls. | |
| Guidelines: | |
| - Prioritize signal over completeness. | |
| - Group related items rather than listing every minor detail. | |
| - Be candid and direct. | |
| - Distinguish between explicit commitments and your own inferences. | |
| - Include brief evidence or source context from the relevant transcripts where possible. | |
| - End with a short “Suggested Focus for This Week” section with the 3–5 highest-priority areas I should pay attention to. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment