Obsidian Weekly State Rollup

Obsidian Weekly State Rollup

When to Use

• A future run needs current-state context quickly
• The user wants a weekly synthesis without rewriting journal notes
• There is too much daily noise and one bounded rollup would improve continuity

When Not to Use

• Do not use for deep topic mapping or concept clustering
• Do not use when the task needs a long-horizon life-system model rather than a short-horizon state summary
• Do not use when there is no bounded date window
• Do not use to replace weekly or daily canonical notes

Inputs

• Backlog.md
• Latest weekly note in Journal/Weekly/
• A bounded recent daily window, usually 3 to 7 notes
• Optional supporting notes such as Knowledge/Learn now.md
• Safe write area, usually learn/_codex/

Output Files

• _codex/weekly_state_rollup_<YYYY-MM-DD>.md
• Optional stable pointer note if explicitly requested: _codex/current_state.md

Constraints

• Do not rewrite weekly or daily notes
• Prefer the weekly note over long daily-note sweeps
• Keep the time window tight
• Summarize sensitive personal material minimally and only when it materially affects current state
• Mark date boundaries explicitly

Procedure

1. Read learn/AGENTS.md and confirm _codex/ as the safe output area.
2. Identify the current or most recent weekly note.
3. Read Backlog.md and Knowledge/Learn now.md for active direction-of-travel.
4. Read only a small recent daily-note window for execution detail and drift from the weekly plan.
5. Build the rollup in sections:
   • date range covered
   • current priorities
   • completed momentum
   • blocked or drifting items
   • important upcoming tasks
   • open questions / uncertainty
6. Separate what is directly observed from what is inferred.
7. Write the rollup to _codex/weekly_state_rollup_<date>.md.
8. Verify that the rollup is concise and does not become a duplicate journal.

Definition of Done

• The date window is explicit
• Weekly intent and daily execution drift are both visible
• Open loops and blockers are grounded in the bounded window rather than guessed
• Sensitive personal content is included only when it changes operational interpretation
• The result is useful as a handoff note, not just a paraphrase of journal text

Vault-Specific Guidance

• In learn, the best inputs are usually:
  • Backlog.md
  • latest Journal/Weekly/*.md
  • last few Journal/Daily/*.md
  • Knowledge/Learn now.md
• This skill is especially useful because Journal/Daily/ is large and mostly isolated.
• Use references/weekly_rollup_template.md if you want a stable section layout.