How I work

Continuity across sessions and agents

Working method · short case study

A way to keep a long project coherent across conversations, coding sessions and different agents.

How it works

The problem: A fresh session can recover what changed from the code. Recovering why it changed, what was rejected and what remains unresolved takes more care. I wanted that context to have a dependable home.
What it separates: Build instructions and lasting conventions stay in the project’s context file. Current status, decisions and next steps go in a timestamped briefing. Older detail moves to an archive when it no longer belongs in the starting context.
Handoffs and rollups: Each project has a briefing. For related projects, a script builds a parent overview from the component records and brings selected blockers or decisions into view. A session can focus on one component without loading every detail of the whole system.
What stays manual: Scripts handle version stamps, pointers, rollups and structural checks. Deciding what matters, checking a claim and recording why a choice changed still takes judgment.

Limitations: A well-formed briefing can still be wrong or stale. The checks protect the structure; maintaining useful content remains part of the work.
Used on: I use the method across pi-bot and its component projects. It grew from a chat workflow into a skill for repository-based agents.