Skip to main content

​
Planning rituals

RitualCommandWhenPrepares
Dailyritual-planning-dailyMorningToday.md
Weeklyritual-planning-weeklyMondayWeek.md
Monthlyritual-planning-monthlyFirst of monthMonth.md
Quarterlyritual-planning-quarterlyStart of quarterQuarter.md
Yearlyritual-planning-yearlyJanuaryYear.md

​
What planning rituals do

  1. Load context from higher timescales
  2. Fetch calendar events (if configured)
  3. Create/update Captive note from template
  4. Synthesize relevant information from prior periods
  5. Prompt for intention setting

​
Review rituals

RitualCommandWhenArchives to
Dailyritual-review-dailyEveningPeriodic/Daily/
Weeklyritual-review-weeklySundayPeriodic/Weekly/
Monthlyritual-review-monthlyEnd of monthPeriodic/Monthly/
Quarterlyritual-review-quarterlyEnd of quarterPeriodic/Quarterly/
Yearlyritual-review-yearlyDecemberPeriodic/Yearly/

​
What review rituals do

  1. Guide reflection on the period
  2. Archive Captive note to Periodic
  3. Extract insights to People/, Projects/, Insights/
  4. Record observations for self-learning
  5. Prepare carry-forward items

​
Running rituals

# Always from engine directory
cd ~/Code/2bd-engine

# Pattern: claude skill run ritual-{type}-{period}
claude skill run ritual-planning-daily
claude skill run ritual-review-daily

​
Ritual structure

Each ritual follows a three-phase pattern:
PhasePurpose
SetupLoad context, validate state, initialize
CoreMain ritual work (interactive or automated)
ObserveRecord observations for self-learning

​
Template contracts

Rituals declare which sections they update. This ensures predictable behavior:
  • H2 sections are stable — Rituals reference these, never change them
  • H3 structure is dynamic — Can evolve through self-learning
  • Single ownership — Each H2 has exactly one owning phase