Interesting ideas! I like the pair idea as well.
I wondered if there are any tools out there that do anything like this:
https://www.perplexity.ai/search/are-there-any-ai-tools-that-im-b54A7CIzSjmPhmDLw7H9Rg#0
One of my associates likes writing pseudo code and comments in the actual code to drive AI. This provides a little more precise way to provide guidance and gets you closer to interacting at the code level. (Jack, you care to comment on this?)
I should add a command to my plugin to support pseudo/comment driven changes.
Perhaps the flow could be:
- Document
- Plan
- Implement tests (TDD)
- Pseudo (modify/improve tests by inserting comments/pseudo code)
- Implement
- Pseudo (modify actual code by inserting comments/pseudo code)
- Get tests passing
- Update docs/plan (to reflect actual implementation)
I find the more I can avoid prompting, the better the experience.