Commands make operating intent repeatable
A named CLI operation is easier to document and repeat than an undocumented sequence of manual steps.
Menus should mirror operational domains
Grouping system, security, application, Fleet and network work helps operators discover commands without flattening unrelated tasks into one enormous reference.
Keep the primitive visible
A shell orchestration layer is most useful when it reduces syntax burden without hiding the files, services and Linux tools underneath.
Automation benefits from explicit boundaries
Different recovery, networking, hosting and virtualisation workflows deserve separate lifecycle rules instead of one generic action that tries to do everything.