Keep Claude aligned on big coding projects with upfront docs, long sessions
This workflow addresses a common problem when working with Claude on complex coding projects: the agent loses alignment with the project's goals or loses track of context partway through. The core idea is to write structured documents before starting work — a 'Technical Brief' and a 'The Point Brief' — that clearly lay out the project's goals and plan. Doing this upfront helps the agent deeply understand the big picture and stay aligned as work progresses.
It also argues for favoring one continuous, long session over splitting work across multiple shorter agent sessions (), because staying in a single session preserves coherence and a working 'feel' for the codebase. The approach is also framed as helping make more efficient use of .
Key points
- Write structured 'Technical Brief' and 'The Point Brief' documents before starting work to define project goals
- Upfront improves agent alignment and reduces context loss
- Favors one long continuous session over splitting work across multiple shorter agents
- Continuous sessions preserve coherence and a working feel for the codebase
- Framed as also helping optimize usage within rate/