43 lines
2.1 KiB
Markdown
43 lines
2.1 KiB
Markdown
# Weekly Template
|
|
You are given the following context for my week:
|
|
$ARGUMENTS
|
|
|
|
## Step 0: Clean up previous week's daily notes
|
|
Ask the user if they want to delete the previous week's daily notes from the ./Daily Notes folder.
|
|
If they say yes, delete all daily notes from the previous week (7 days prior).
|
|
|
|
## Step 1: Create the weekly note
|
|
Please create a new note in the "Weekly Notes" folder.
|
|
The title should be "Weekly Note - Month, Day Year" using today's date.
|
|
|
|
## Step 2: Review Notion data and create the note
|
|
First, use the Notion MCP to review the Projects and Task Tracker to get insight into focus areas for this week.
|
|
|
|
List all projects with status active and ask me which 3 i want to prioritize for thie upcoming week.
|
|
If there isn't a weekly goal for the selected projects, ask me to write one.
|
|
Update the Focus this week field to true for the selected projects.
|
|
|
|
Then add the following to the note
|
|
|
|
|
|
Format the note with the following sections:
|
|
1. **Priorities for this week** - List the three projects I selected with their weekly goal.
|
|
2. **Key tasks** - List all tasks that are due this week. Order by due date and blocker status. Show the task name, related project, type, and effort level. Provide a link to the task in Notion.
|
|
|
|
## Step 3: Generate my reading list
|
|
Then, query the Reading List database (collection://2c4abd6c-450a-804a-809a-000bc77d02c1) for articles with Status = "To Read" or "In Progress".
|
|
|
|
3. Under **Suggested Reading** recommend 2 articles that fit the available time blocks:
|
|
- Look at the unscheduled time blocks to determine what reading time is appropriate
|
|
- Match articles based on Read time field:
|
|
* Short = <5 minutes (fits in small gaps)
|
|
* Medium = <15 minutes (needs decent gap)
|
|
* Long = >15 minutes (needs larger block)
|
|
- For each article show: Title, Topic, Read time, and URL
|
|
- Briefly explain why these articles fit tomorrow's schedule
|
|
|
|
|
|
## Formatting Rules
|
|
* Always provide a tl;dr summary at the top of the note
|
|
* Add a "## Table of Contents" section after the frontmatter using Obsidian internal link syntax `[[#Heading Name]]` for all H2 sections (if there are more than 3 H2 sections)
|