I was looking at creating am auton selector for the brain but I have no idea what to do to create the selectable buttons or have it switch to the next screen. Would anyone be willing to show me what you have done or what I could do to accomplish this task?
One to get you going.
and extension to jpearman’s example was this
this allowed lots of situations. This past season my teams adapted it to VEXcode blocks.
There is a lot you can do, and it depends how you want to work with your team. One thing our teams have learnt the hard way, press the wrong button and your robot does a back flip during autonomous and dead for remainder of match. Check lists are your friend 
Yup, kids figured this out last season.
Was ready to spend summer to design an example pizza ordering system using V5 coding platforms - but you know, life happens.
Let me know if Pizza ordering system might be a good example for me to develop.
Quick question, if you have made an autonomous selector, how would you go and test it? Is there any way to do it without being at a competition or using a competition switch?
We usually have it active at all times, including prior to, during, and after the autonomous period (including when the competition is not active). If you want to be safe about it, you can set a boolean once autonomous starts to disable the buttons.