follow-up

Handle pending reminders and project follow-up entries. Three modes: bare (/follow-up), cron-fired (/follow-up due <id>), and review (/follow-up review).

Spec: docs/spec/cron-workflow.md § /follow-up

<reminders-dir> below is atomic where --json's reminders field when the atomic binary is present, else the .claude/.scratchpad/reminders/ fallback dir used when it is absent — the legacy path reminder.List already unions and atomic migrate already relocates. Paths come from atomic scratchpad / atomic where --json; if what you find on disk does not match, run atomic migrate --show-log for the change history.

Mode detection

Inspect $ARGUMENTS:

• Empty → bare flow (interactive list, steps 1–6 below).
• due <id> → cron-fired flow (steps A–D below).
• review → review flow (steps R1–R6 below).

---

Bare flow

Step 1 — Build the indexed reminder list

Detect binary:

• Binary present (command -v atomic exits 0):

  atomic reminder list
  

  Output is indexed and includes the transport column. Capture it.

• Fallback (binary absent): list and parse files manually:

  ls .claude/.scratchpad/reminders/*.md 2>/dev/null
  

  For each file, extract frontmatter fields via grep:

  grep -m1 '^id:'        <file>   # → id
  grep -m1 '^created:'   <file>   # → created timestamp
  grep -m1 '^transport:' <file>   # → transport (cron|routine|none)
  

  Then read the body (lines after the closing ---). Build an indexed list from those fields.

  If no files found: print no reminders. and exit.

Step 2 — Optionally enrich with schedule info

For each reminder, attempt to find its live schedule entry:

• cron transport: call CronList and search for an entry whose prompt contains /follow-up due <id>. If found, note the next-fire time as "fires in X" or "fires at ".
• routine transport: if a routine listing is accessible, search for an entry with the matching prompt. Note fire time if found.
• none transport: no schedule lookup needed. The reminder will surface via the session-start hook only.