Couple DX feedback: 1. I love

spin

type. It makes it feel like a native

atmos

command. However, it hide error messages. It needs a way to surface an error on non-zero exits. a. Adding the ability to pass state (eg, outputs) that can be used by another step would be a bonus. 2. Support for GitHub Action style

if:

condition for steps would be useful. a. Not really needed for

shell

or

spin

type steps, but it would be useful for

choice

types. It would allow for similar interactive experience that

atmos

provides when running commands that required stack or component inputs. eg, custom command that has flag marked optional (but really is required) could prompt user to select a option when flag value is a empty value. 3. Support for dynamic

options

for

choice

a. We already discussed this. I just haven't spent time on solving it yet. Probably will start this evening.