# Add allow\_skipping flag to plays **URL:** \ **Category:** Ansible Developer\ **Created:** [September 25, 2014, 4:23am UTC](https://forum.ansible.com/t/add-allow-skipping-flag-to-plays/16330 "2014-09-25T04:23:30Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Tony\_Kinsley](https://avatars.discourse-cdn.com/v4/letter/t/b19c9b/32.png) [@Tony\_Kinsley](https://forum.ansible.com/u/Tony_Kinsley)\ **Post date:** [September 25, 2014, 4:23am UTC](https://forum.ansible.com/t/add-allow-skipping-flag-to-plays/16330/1 "2014-09-25T04:23:30Z")
I currently have a playbook that the first play provisions VMs and then uses set\_facts to set the ansible\_ssh\_host to the ip returned from the provisioning step. I really like the --start-at-task option, especially while developing my playbooks, however if I skip the first play then I cannot access any of the hosts. This also means all my tags cannot work. I went to implement a dynamic inventory but this feels like I am just duplicating exactly what the playbook is doing anyways. Instead I was wondering if anybody liked the idea of adding an allow\_skipping flag to plays that could force the play to be run no matter what. For instance, ` ---
**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\ **Post date:** [October 1, 2014, 12:35pm UTC](https://forum.ansible.com/t/add-allow-skipping-flag-to-plays/16330/2 "2014-10-01T12:35:48Z")
We generally try to push back on having a lot of new language keywords The general suggestion is to tag all things as “common” on the play and get in the habit of tagging things “common” There has been a recent PR to add an “all” tag that would not have to specified, and ensure things always get run when tagged with all. This would be a better way to do it, IMHO, as it avoids a new language keyword. Hope that makes sense!