[Jugurtha]

Something useful is to write the copy for the future project. Writing the draft for the docs too as if the project was already shipped. It helps a lot with focus and alignment. Making sure we want to build the same thing. Adding new ideas. This is basically a period with no constraint as no code is written yet and no sunk cost to hinder your thoughts.

A useful exercise is to imagine you're making a tour video showing off what the product does. What would be in that video, and then the code to write to make that happen becomes clearer.

Also, reflecting on the project that was done and all the hidden skeletons can be useful. The mistakes and inefficiencies. How to avoid those in the new project? For example: it was super hard to add functionality or remove it in the previous project. The next project starts by being extensible, with a plug-in architecture with zero change to add am extension. You write how you would add extensions and then write the code to allow that flow.

How to transfer the learning from the previous project on to the next one, and just individually but as a team.