Comment by hombre_fatal
10 days ago
Everything but trivial changes should go through a prompt -> plan -> impl phase where you revise a concrete plan file until it's ready for impl.
Now impl is just a derivation of the plan, and the plan gets checked in with the same commit so that you can see the why, the intent, the objective, the research that informed the decisions.
Much simpler, and a much, much more effective process than prompt -> impl.
Exactly right, and the next step is making it enforceable rather than aspirational. Restrict the plan phase to read-only tools so the agent literally can't edit during planning. Restrict the impl phase to the edit tools the plan identified. Even this basic formalization: same model, same task... yielded a dramatic capability improvement on sub-20B models in my testing.
yep. i built recursive-mode for this. it offers full traceability with workflow run docs that are human-readable. as a bonus, you can also use this to train or finetune your model. https://recursive-mode.dev/introduction