[aerugo_]

Interesting! Did you publish it? It’s a great idea to prioritize based on git history.

As for multiple stages, it means the tool itself is doing a few calls to the model. What do the code summaries look like? Just function and class doctrings? Getting the model to write summaries that are comprehensive enough to guide development but still more compact than the code itself seems like it may not be a trivial problem.