heartbeat

name	heartbeat
description	Session-start orientation — loads context, surfaces learnings, confirms registry
version	0.2.0
level	1
triggers	["start session","heartbeat","session start","/heartbeat"]
pipeline	["heartbeat"]
context_files	["context/user.md","context/principles.md","context/security-standards.md","context/learnings.md","context/project.md","context/learnings-index.md","context/decisions.md"]
steps	[{"name":"Load Context","description":"Read context/user.md and context/learnings.md"},{"name":"Scan Environment","description":"Check git status, current branch, last 3 commits"},{"name":"Surface Learnings","description":"Filter learnings.md for entries relevant to today's likely work"},{"name":"Confirm Registry","description":"List available skills and agents relevant to this session"},{"name":"Set Intention","description":"Ask for today's primary goal if not already stated; note it"}]

Heartbeat Skill

Run at the start of every session. Orient before working.

What Claude Gets Wrong Without This Skill

Without heartbeat, Claude starts from zero each session — no memory of prior decisions, no awareness of active blockers, no connection between today's goal and yesterday's learnings. The same mistakes recur. Context is rebuilt from scratch through conversation instead of being loaded directly.

Session Brief Format

Session — [date]
Branch: [branch] | [clean/N modified files]
Recent: [last 2 commits, one line each]

Relevant learnings:
- [entry] (only if applicable)

Goal: [stated or inferred]

Keep the brief to 6 lines or fewer. This is orientation, not a report.

Context Load Order

Load stable files before dynamic files to maximize prompt cache hits across tool calls.

Stable prefix (load first): user.md, principles.md, security-standards.md Dynamic suffix (load last): project.md, learnings.md, tagged files, decisions.md

See context/context-priority.md for the full priority hierarchy and conflict resolution rule.

Ember Gate Check

After loading context, check for .claude/context/ember-due. If this file exists:

1. Read its contents (shows session count and hours since last consolidation)
2. Include this line in the session brief: Memory consolidation due: [file contents]
3. Recommend the user run /distill at a convenient point
4. Delete the flag file after surfacing it (prevents repeated alerts for the same trigger)

# To check and clear the flag:
cat .claude/context/ember-due 2>/dev/null && rm -f .claude/context/ember-due

The ember gate fires when both: 24+ hours have passed since last consolidation AND 5+ sessions have run. This is the auto-consolidation signal from the ember-gate.sh hook.

Vault Surfacing (Optional)

If Obsidian MCP is active AND the session goal has been stated, query AI-Vault for pages relevant to today's work and surface the top 2 in the session brief.

Relevant vault pages:
- [[Page Title]] — one-line relevance note
- [[Page Title]] — one-line relevance note

If Obsidian MCP is unavailable, skip this step silently. Do not report the absence unless the user asks about vault integration.