[Joker_vD]

GUIs have "discoverability" and "affordances". I've haven't read a single help file for any GUI application in 20 years (including apps on Windows, Linux, and Android) and somehow I can navigate and use them perfectly fine.

That's simply impossible with CLIs, you need at least read a "How to Get Started Immediately" note.

[AnIdiotOnTheNet]

PowerShell does an okay job at command line discoverability in my experience. When using a cmdlet I'll think "I hope there's an argument for X" and then I can hit tab after '-' and cycle through all the available arguments. As another post mentioned, this unfortunately falls down a bit with cmdlet names themselves because they start with the verb instead of the noun: Get-<tab> isn't helpful the way NetAdapter-<tab> would be.

[SAI_Peregrinus]

Fish is similar in this way, if you're not on Windows and thus don't have access to PowerShell.

[AnIdiotOnTheNet]

PowerShell is available for Linux.

There's also Elvish, Nushell, and a few other attempts in a similar vein.

[majkinetor]

I take 'similar vein' as grand euphemism.

[majkinetor]

PowerShell is besides Linux also available on Unix.

[ogogmad]

Unix is a family of OSes that includes Linux in particular.

[majkinetor]

Cycling tabs is not effective. PSreadline supports CTRL+SPACE completition - just type - and then CTRL+SPACE and it will show menu with ALL arguments. The same works if you start argument (i.e. -P<CTRL+SPACE> shows all params starting with P)

[OldHand2018]

Ctrl-Space on PowerShell is outstanding, as long as your devs are actually properly commenting their scripts (I assume your in-house PowerShell is put into modules that get installed on user machines).

[majkinetor]

It has no relation to comments.