Keeping RFCs in Github issues
I was writing RFCs as markdown in my project to describe features I want to work on. This allows me brainstorm and refine and sketch out some diagrams and prototype code.
After reading Simon Willison's strategies for project management, I switched to using issues for RFCs. As long as I'm just conversing with myself, the friction of using issues is much lower. I can just write up thoughts and add to an existing thread instead of editing a markdown, keeping a log of what I changed, and committing it to the main branch.
This would be different in a team context, as I would have to put some thought into the actual document. Even then, I would actually use an out-of-tree tool like google docs, hackmd or obsidian until a reasonably legible document was ready to be merged as an RFC and later on as an ADR.