Session Handoff
You open a cold session tomorrow and it already knows the repo, the decisions, the blockers, and the next action.
Your agent session is full. Tomorrow you open a new one and spend the first hour re-explaining the project.
Northstar Inventory
Watch it work
Ending a long session on a fictional inventory app. Invented company, invented data. Nothing here comes from a live account.
You
Your AI
Running Session Handoff
- Decisions captured — 4 recorded
- Blockers captured — 1 open
- Handoff written
- Next-session prompt ready
What you get back
HANDOFF_2026-08-20.md
where you stopped and why
SESSION_LOOKBACK.md
the running project history
launch-prompt.txt
paste to resume tomorrow
Demonstration only. Fictional project, no real account or credentials.
The difference
Without it
- New session opens cold
- You retype the context from memory
- Old decisions get quietly re-litigated
- First hour goes to reorientation
With it
- New session reads one file
- Repo, branch and milestone already known
- Decisions carried forward, not repeated
- First message is the next real task
Give it this, get this back
You give it
A session that is about to end.
It runs
Ending a long session on a fictional inventory app
You get back
A handoff file, a running lookback, and a launch prompt for the next session.
So that
You open a cold session tomorrow and it already knows the repo, the decisions, the blockers, and the next action.
The same run, as files and output
›/session-handoff›reading session state...›repo northstar-inventory (branch: feat/stock-alerts)›milestone M2 low-stock alerts -> complete›decisions 4 recorded›blockers 1 open›wrote HANDOFF_2026-08-20.md›updated SESSION_LOOKBACK.md›launch prompt ready to paste
the state of play
## Where we are Branch feat/stock-alerts. M2 complete, tests green. ## Decisions D-011 alert threshold is per-SKU, not global D-012 email digest daily, no per-event sends ## Blocker Supplier feed returns stock as a string. Needs a parser before M3 can start. ## Next action Write the feed parser in lib/supplier-feed.ts
the running history
2026-08-20 M2 low-stock alerts shipped 2026-08-18 switched alerting to per-SKU thresholds 2026-08-15 M1 stock ledger shipped
paste into the next session
You are resuming Northstar Inventory. Read HANDOFF_2026-08-20.md first. Start with the supplier feed parser.
Without it
- New session opens cold
- You retype the context from memory
- Old decisions get quietly re-litigated
- First hour goes to reorientation
With it
- New session reads one file
- Repo, branch and milestone already known
- Decisions carried forward, not repeated
- First message is the next real task
Exactly what you download
session-handoff/ ├── .lookback-config.template.json ├── README.md ├── SKILL.md └── scripts/ (1 files)
Generated from the real product file.
Your terms
- One-time purchase. No subscription, nothing to cancel.
- Use it in your own business and on client work.
- Change it however you like. The files are yours to keep.
- Download link emailed immediately. It works for 30 days.
- Full license · 14-day guarantee
Works with your AI
Pick where you use AI
Drop the folder into .claude/skills/. This is the format the files are written in, so nothing needs converting.
mkdir -p .claude/skills cp -r session-handoff .claude/skills/
Every skill is plain markdown plus its references and scripts. Any AI tool that can read a rules or context file can run it. The tiers above say where we have actually checked.
Pairs well with
Ready when you are
You open a cold session tomorrow and it already knows the repo, the decisions, the blockers, and the next action.
14 days to change your mind. Email support@anvilroad.com and we refund it.