# Task prefix

**URL:** <https://forum.ansible.com/t/task-prefix/19069>\
**Category:** Ansible Project\
**Created:** [August 20, 2015, 5:02am UTC](https://forum.ansible.com/t/task-prefix/19069 "2015-08-20T05:02:06Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Francisco\_Garcia](https://avatars.discourse-cdn.com/v4/letter/f/aca169/32.png) [@Francisco\_Garcia](https://forum.ansible.com/u/Francisco_Garcia)\
**Post date:** [August 20, 2015, 5:02am UTC](https://forum.ansible.com/t/task-prefix/19069/1 "2015-08-20T05:02:06Z")

</div>

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?