@sarah11918Sarah Rainsberger 
@ayo Wow! I had no idea Astro used this approach too. The concept of an API docs bash is brilliant! I completely agree that creating docs first helps validate the user experience early and dramatically improves development efficiency. Honestly, I didn't realize this was a more common practice. I'd love to hear more about your RFC process! Are there any blog posts or public resources about Astro's documentation workflow?
@hongminhee洪 民憙 (Hong Minhee) @ayo We have a roadmap repo for the RFC process: https://github.com/withastro/roadmap
We often have pretty good minimal user docs in the Stage 3/proposal, but even Stage 1 to just propose something encourages adding "end-goal" code examples of what it could look like if you're updating/changing/creating an API.
As for writing about our docs workflow, we've mostly focused on our community contributor process & guides like Astro Docs Docs (AD²) https://contribute.docs.astro.build , but a great idea!
If you have a fediverse account, you can quote this note from your own instance. Search https://mastodon.social/users/sarah11918/statuses/114364247773706554 on your instance and quote it. (Note that quoting is not supported in Mastodon.)