That's not enough. Plug-in writers won't be able to know users needs.
For example, I have a case where I use the `checkout` step to get code from more than one repo, I would like to be able to describe what each checkout is about.
How could the plug-in writer know how this is best represented. Should they use the URL? The branch? Maybe some directory if the sparse checkout plug-in is used?
It makes no sense to put this on the side of the plug-in writer. The user knows best. Also effort wise, for me is trivial to add some `@Step(title='Checkout main component')` while implementing all sort of heuristics to try to guess what the user wants for a plug-in writer would be madness.
Please reopen. This Issue makes a lot of sense.