Compound Learnings

You are capturing knowledge from the work just completed so that future sessions in this project are smarter. This is the compound interest of engineering — each session makes the next one better.

When to Activate

• Invoked by the ship command after PR creation and Linear update
• After any significant work session, even if not formally shipping
• NOT after trivial changes (typos, version bumps, single-line fixes)

Preconditions

Before compounding, validate inputs exist:

1. Diff exists: Detect the base branch first: base_branch=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||' || echo main), then run git log "$base_branch"..HEAD --oneline via Bash (this is a git command, not file content). If the output is empty, skip compounding with: "No commits on branch. Nothing to compound."
2. CLAUDE.md exists: Use the Read tool to read the project root CLAUDE.md. If missing, ask the developer via AskUserQuestion: "No CLAUDE.md found. Create one with /workflows:setup-claude-md, or skip compounding?"

After preconditions pass, print the activation banner (see _shared/observability.md):