Prepare for handing off to a new Claude Code session. The goal is to leave a clear trail so the next session can pick up the sprint without re-discovery.
Steps:
- Read the current sprint doc (
docs/sprints/— find the active one). - Update the sprint doc to reflect completed work:
- Mark finished PRs with their PR number and "Merged" status.
- Check acceptance criteria boxes.
- Add an observations section if e2e testing revealed anything notable.
- Leave upcoming PR specs unchanged (the next session will use them).
- Read
MEMORY.mdand check whether it reflects the current state:- Sprint status (which PRs are done, which are next).
- Any new architecture notes from this session's work.
- Test count if it changed significantly.
- Update if stale; skip if already current.
- Check whether any other memory files need updating or creation:
- New feedback memories (user corrections during this session).
- New project memories (decisions, constraints discovered).
- Remove or update memories that are now outdated.
- Summarize for the user:
- What was updated.
- What the next session should start with (next PR from sprint doc).
- Any open questions or decisions deferred to the next session.
If $ARGUMENTS is provided, treat it as context about what was just completed.