Task prefix

There is a pattern which I like and see an several playbooks, something like this:

  • name: ANSISTRANO | Ensure deployment base path exists
The goal is to prefix a set of related patterns so the user can quickly identify their context

Is there any plan to implement a feature to ease this pattern and avoid this manual hack? Like a push/pop prefix or block-auto prefix?