Splitting Planning and Execution in a Claude Code and DeepSeek Pipeline

Somewhere around the third feature request in a row, I noticed I was burning a full Claude Code session on work that did not need it. Adding a pagination parameter to an endpoint. Renaming a serializer field across four files. Tasks with a clear answer and almost no judgment involved, running through the same model I use to decide whether a migration is safe or whether a query pattern will lock a table in production. That mismatch is what pushed me toward a two model pipeline: Claude Code…