Workflow

workflow — Claude Code sessions that pick up where the last one left off

Every Claude Code session starts with an empty context. The usual fix is a notes file the agent updates at night and
reads in the morning. It works until the notes are wrong: a branch "pushed" that never reached the remote, a job
"still running" that died at 1 a.m., a to-do that shipped last week. The next session believes them.

This template checks the notes against the facts at every start. The handoff is a claim; the script is the fact.

- /session-start reads git, GitHub and the machine (ground-truth.sh): each repo and branch against its remote,
  open PRs and their CI, the items other sessions claimed, background jobs. Then the last handoff: it reports where
  they disagree, proposes the day's task, and waits for you.
- /handoff runs the same script and records where things stand, for the next session on any machine.
- /board shows the backlog, your decisions, the lessons and the handoffs as one page that updates itself.
- /autonomy sets what Claude does without asking you: commit, push, open or merge a PR, release, …
- /checks sets how the code is checked before a merge (its tests, GitHub CI, both) and the rules you keep.
- /trim proposes what to keep, shorten or delete once your rulings and lessons grow.

What it looks like

Monday morning, /session-start on a project whose last session ended on Friday:

A session that trusted Friday's note alone would have asked for a red PR to be merged, reported the backfill as
done, and rewritten code that already existed. Every file behind this brief is in example/.

Quick start

You need bash, git and a remote for your project; optionally the GitHub CLI gh (PRs and CI) and systemd
(background jobs). Linux, macOS, and Windows in Git Bash or…