Lettuce Docs Tags Graph

Weekly review

#docs#recipes#agents
~4 min read

Weekly review

A GTD-style weekly review, automated as much as possible. Friday afternoon, you get a structured note with everything you need to reflect on.

What it produces

Reviews/Week YYYY-WW.md containing:

Setup

A schedule rule drops a > [!ai] directive into a target note every Friday afternoon. The schedule itself does no AI work — when the rule fires, the poller splices the prompt below into target as a directive, and whatever MCP agent you have connected (Claude Desktop/Code) picks it up via pending_directives and does the gathering. (See Vault automation/02 Schedules for the full schema.)

# .lettuce/schedules.yml
- weekly: "Fri 16:00"
  target: "Reviews/Week {{year}}-W{{week}}.md"
  prompt: |
    Build this week's review note. Create the file if it doesn't exist;
    overwrite the generated sections if it does. Use the search tool to gather
    everything below, then fill these sections:

    ### What I shipped this week

    - Notes whose frontmatter `status:` is "shipped" or "finished" and were
      modified in the last 7 days.
    - Book notes with status: finished this week.
    - Completed `- [x]` tasks in Daily/* notes.

    ### What I learned

    - Notes created in the last 7 days under Notes/ or Notes/Atomic/.
    - For each, paste the first paragraph as a preview.

    ### What I owe

    - Search for "- [ ] @baher:" across the whole vault.
    - List as wikilinks back to the source notes.

    ### What's stuck

    - Notes tagged #blocked or #risk.
    - Also: projects with status: active not touched in 7+ days.

    ### What's next

    - Projects with a deadline within 14 days, status: active.

    ### Open questions

    - Blockquotes starting with `[!question]`.

    ### Reflection prompts

    (Leave blank for me to fill in)

    - What went well this week?
    - What did I avoid?
    - What's one thing to change next week?

The {{year}} and {{week}} tokens in target are resolved at fire time (Gregorian calendar year and two-digit week-of-year), so each Friday’s directive lands in a fresh Reviews/Week 2026-W22.md-style note. Note: target templating covers only {{date}}/{{year}}/{{week}}; the prompt text is spliced verbatim, so anything date-dependent inside the review (like “the last 7 days”) is computed by the connected agent when it runs.

Why it works

The agent does the gathering — the part that’s tedious and error-prone — and leaves you with the reflection. You spend 15 minutes thinking, not 60 minutes scrolling.

The “open questions” section pulls from > [!question] callouts so you can sprinkle questions throughout the week and they collect themselves on Friday:

> [!question]
> Should we open-source the LSP plugin?

Variations

Daily reviews

- daily: "21:00"
  target: "Reviews/Day {{date}}.md"
  prompt: |
    Build today's review note. Same shape as the weekly review, scoped to
    today. Create the file if it doesn't exist.

Useful for people who do daily, not weekly, reflection. {{date}} resolves to the fire date as YYYY-MM-DD.

Prompts that adapt

Add a coaching section to the weekly prompt above. The schedule can’t read prior reviews itself, so you ask the connected agent to do it:

    At the end, add a "## Coaching prompt" section. Read the previous week's
    review note (Reviews/Week ...-W..md) if it exists. If I wrote reflections
    there, identify a pattern (e.g. a recurring theme of "avoided X") and pose
    one targeted question. Otherwise ask: "What's the most important thing for
    me to remember as I plan next week?"

This makes the review evolve as your vault accumulates context.

Quarterly rollups

The schedule fires every Sunday evening, and the agent decides whether it’s the last Sunday of a quarter (there are no calendar predicates in the schema, so this judgement happens in the prompt):

- weekly: "Sun 19:00"
  target: "Reviews/Quarterly check.md"
  prompt: |
    If today is the last Sunday of a quarter (Q1 ends Mar 31, Q2 Jun 30,
    Q3 Sep 30, Q4 Dec 31), write Reviews/Quarter <year>-Q<n>.md by reading the
    13 weekly reviews of the quarter and synthesising:
    - Top 5 ships
    - Top 3 patterns of stuckness
    - Quarter-over-quarter velocity
    Otherwise, do nothing.

Because the directive always lands in the same fixed target, give the agent an explicit instruction to write the dated quarter note itself and leave the target note untouched on non-quarter-end Sundays.