A workflow for managing large Claude Code projects across multiple sessions using plan mode, Domain-Driven Design discovery, and living PRD/ERD documents. The approach starts with a DDD-lens conversation in plan mode to surface ambiguities before writing any code, then produces a Product Requirements Document (PRD) capturing the 'why' and an Engineering Requirements Document (ERD) with phased, atomic tickets tracking progress. The ERD acts as a session handoff artifact — new sessions simply read the documents and pick up the next unchecked ticket, eliminating the need to re-explain context. This also enables parallel Claude agents to work independently on different tickets using the same shared plan.
Table of contents
Step Zero: Plan ModeWhy use DDD as the lensThen, and Only Then: PRD and ERDWhy the ERD is a living documentWhat This Buys MeA Typical Opening SequenceWhat a Resumed Session Looks LikeMy thoughts on experimenting with this flowSort: