This looks very promising and less "magical" 👍🏻

DescribableCommandInterface should not be needed IMHO

with >=php8 we can argue attributes are superior either way, and thus we're targetting php7 only

It's really fast to meet the convention from #39851 for the time being (eg. pre-php8 era): $defaultName = 'foo|bar'; and done

From a DX perspective, this requires ppl to implement a new static method to gain laziness, which is more code to write.

#39851 provides a descriptive approach instead, that paves the way to configuring the same thing using attributes on PHP 8. Doing so would be a minor implementation change on top of #39851.

What benefit are you expecting from this approach, vs #39851?

As of now, the proposed CommandDescription looks very much like a PHP 8 attribute in disguise.
If we agree on the target that would be to allow using an attribute for the purposed config settings, then I think #39851 is more aligned to this goal.

What benefit are you expecting from this approach

Cleaner, extensible (ie. allows enabled), self explanatory (|foo|bar is not obviously a hidden command).

If we agree on the target that would be to allow using an attribute for the purposed config settings, then I think #39851 is more aligned to this goal.

I totally agree with this comment (and similar from @ro0NL), if we target php8 attributes, that would make sens to move with #39851 and make the migration smoother

Cleaner, extensible (ie. allows enabled), self explanatory (|foo|bar is not obviously a hidden command).

On my side, it looks like more code boilerplate for something that could be just plain descriptive.
About the "self-explanatory" part, it's a very minor thing, and the attribute will improve this anyway.

Closing in favor of #39851 and a path to php8 attributes