LLMs are unreliable, which is why I use the plan pattern
1. describe what you want in a paragraph or two
2. tell it to write a plan.md, iterate and review multiple times
3. implement and test, iterate and review multiple times
Putting in more effort upfront, human in the loop planning, has a higher probability of getting out something you want, in my (vibes based) experience. Use many fresh sessions and different models for this. You want them to focus more on the current state, the intent of the changes, the complexities. What you don't want is a step-by-step plan for changing the code, which effectively is putting the thinkin / implementation in markdown first. The implementation will go much better with a well designed and vetted plan. This is where I spend more of my effort these days.
KISS but detailed enough to provide framing and guidelines without being prescriptive, because we know humans too miss edge cases and need to rethink or pivot strategies.
LLMs are unreliable, which is why I use the plan pattern
1. describe what you want in a paragraph or two
2. tell it to write a plan.md, iterate and review multiple times
3. implement and test, iterate and review multiple times
Putting in more effort upfront, human in the loop planning, has a higher probability of getting out something you want, in my (vibes based) experience. Use many fresh sessions and different models for this. You want them to focus more on the current state, the intent of the changes, the complexities. What you don't want is a step-by-step plan for changing the code, which effectively is putting the thinkin / implementation in markdown first. The implementation will go much better with a well designed and vetted plan. This is where I spend more of my effort these days.
KISS but detailed enough to provide framing and guidelines without being prescriptive, because we know humans too miss edge cases and need to rethink or pivot strategies.