Egregoros

cli tools not just walking me through it and instead having me ace the flags, is really just a niggerlicious holdover from the 80s and I don't care that I'm a noob and don't have 20000 hours grinding away at moldy ass system code.

it should be able to detect if you were running from cli or a shell script, and if it is the former, it should just tell you what it is gonna do if you hit enter, which is the default, and if you want something else just have a little wizard that assembles the command into a line at the bottom so then when you walked through the options, you have
>$ foo --flag-one 12 --flag-two /path/to/file ...
and so on and then you just hit enter and it runs it and you can copy-paste the command for later.

I really don't see what the problem is just doing it like that except it would take a bit of work to set up the wizard. if everything had wizard support though, you could make it be "$ wizard foo" though, instead of "$ man foo" and then it wouldn't really take that long to make one

RT: https://poa.st/objects/d58b406a-d72c-430b-8755-e6a35c5bae4d

@WandererUber
The AI demon is pretty good for finding how to use a command. It doesn't help that viewing troonix manpages is a terrible experience. There's no way to search only the section headers, even if there were there's no way to have “keywords” so that if the program uses different terminology you can still find what you wanted easily, there are no hyperlinks for other manpages, and even if you type a word exactly, it will not match if the line broke in the middle of that word.
>demanding I remember if it was […]
Most shells can be made to have tab‐completion for arguments. Powershell has it out‐of‐the‐box for any functions that you define and for the builtins at least. But there isn't any sort of standard for specifying the argument types and names (that anyone uses, at least) so if there is even a way to get it for external commands it would take a lot of effort on your part.