File/API structure planning steps by default

[Konard]

It is crucial to have a planning step for changes in file structure, and it should have mandatory approval by users by default.
Before we even begin to make changes to files that are bigger than half the context (32k tokens / 2) we should be able to plan changes in each file's public API with mandatory approval by user by default.

Today, with so much limitation, it is almost impossible to make it autonomous.
Every change or plan can be perfected by GPT-4 many times giving it prompt (Can you do better? Can you improve your plan? And so on).
On the other hand, user should be in control of spending via GPT-4 API, and it should be configurable all guided to have that many second thoughts.

Anyway, it will be completely impossible without #31 and #85

Related to #94

[irgolic]

It already plans changes while it looks at files, so this is a duplicate of #87.

What would you think of having two separate triggers, one to iterate the plan in the issue, and one to trigger code generation?