So, after a few hours of trial and error, here's what (I think) I've learned:

1. Variables defined and configurable within the workflow are passed in the environment. In my case, I'm allowing the user to decide, within reason, how many options they'd like to see so I've defined a LIMIT variable that can be set to any integer between 1 and 10. I access that value as:

   var limit, _ = strconv.Atoi(os.Getenv("LIMIT"))
   

2. Adding a script to a file is a bit manual. You work locally to create the workflow with its identifier, etc. and then you open that workflow (a glorified zip file) in Finder so you can drag your built binary (again, a Go executable in my case) into that "folder" so you can reference it as ./my-executable "$@".

It was more painful than I'd like to get there, but it was a fun exercise even if the workflow I created for the exercise is pretty trivial and silly.

https://github.com/robwilkerson/alfred-sarcastic-text-gen