How to avoid plan bloating and token waste #163
Description
This morning I was trying the plugin to develop a feature starting from the plan and the work resulted in a massive bloat of tokens and scope creep.
Interestingly, the plan contained a large number of features that could make sense (i.e. jwt authentication) but that weren't in scope of my request, i.e. for my goal there are much simpler ways to handle some of these problems in the short term, and then improved.
What are the best practices to avoid this re-occurrence?