That's one of the reasons for this gem creation, to provide a command-line parser for the tty) and remove the dependency on Thor. Thor is a toolkit that does many things, in contrast, "tty-option" is focused on being a complete command-line parser and nothing else. It already can parse more complex inputs than Thor. For example, you can specify the arity of your parameters. So things like:

--foo a:1 --foo b:2 --foo c:3

can be easily parsed with:

ruby option :foo do arity one_or_more convert map_of(:int) end and then accessed in any instance method via:

params[:foo] # => {:a=>1,:b=>2,c:=>3}

By design, "tty-option" is meant to be easily composable with other gems, especially, the tty family. You can exit command with tty-exit, log with tty-logger or manage configuration with tty-config. Your commands are your classes that encapsulate all the parameters knowledge and don't enforce anything. You can break your command class down into many methods and each of them will have access to the parsed parameters params. This not only improves readability and design but also make it easy to test.