Note
Minimal process
Keep process small enough that it still helps the work move forward.
Minimal process is the default. If the process gets heavy, it starts competing with the work instead of supporting it.
The standard is simple: the process should help move toward the goal, and anything beyond that needs to justify its own weight. A process that is a little rough but usable is better than a perfect one that slows things down.
In Planning and implementation, the work stays split between planning and doing. Automated dependency updates applies the same idea to maintenance by automating the churn before it turns into a separate project.