warmup

Give Claude continuity across sessions. Each session starts cold; a 30-second digest is cheap context engineering.

When to use

• First substantive message in a vault session.
• User asks “what’s going on”, “where did we leave off”, “summarize recent activity”, or runs /warmup.
• Before a process-inbox or reconcile run (so you know what’s changed recently).

Workflow

1. Read the ## Items section of notifications — count action items and note the oldest date. This becomes the first line of the digest.
2. bash 7_Agent/skills/recent-changes/recent-changes.sh --days 3 — compact folder-grouped summary of recent activity. Commit messages are auto-commit noise; the folder/file delta is what matters.
3. Read the tail of questions (last ~10 entries).
4. Find the most recent 7_Agent/reconcile/<YYYY-Www>-reconcile.md and read its key proposal sections (Consolidation candidates, Promotion candidates, Synthesis).
5. ls 0_Inbox/ and ls 0_Inbox/transcripts/ — count pending items.

Output

A ≤150-word digest, structured:

**⚠️ Notifications:** <N action items outstanding, oldest YYYY-MM-DD (X weeks) — run `/triage`. Omit this line entirely when zero.>
 
**Recent activity:** <1–2 sentences on which PARA areas got touched and any notable moves/renames>
 
**Inbox:** <N items pending, M raw transcripts>
 
**Open questions:** <2–3 most relevant from questions.md, as bullets>
 
**Last reconcile proposals:** <2–3 most actionable, as bullets>

Rules

• Hard cap at 150 words. This is a digest, not a report.
• Lead with what’s new, not what’s stable. The vault doesn’t need re-describing every session.
• Don’t act on anything. This skill is read-only. Proposals become actions only when the user asks.
• If there’s no reconcile report yet, say so and skip that section.

Verification

• Output fits in one screen.
• Word count ≤150.
• No files modified.