I'm creating a starter kit for the Panopoly distro that will generate a skeleton distribution using Panopoly as a base distribution. I'm doing this with a custom drush command. The code can be seen here.
I'm using a STARTERKIT folder that contains all of the code that will be copied and go through string/token replacements. The drush command is working well however what I'm unable to figure out is how to programmatically figure out where the STARTERKIT folder is. Right now I'm relying on the user entering --include=path/to/drush.command option.
Assuming the user copies the whole project to their ~/.drush folder they can run the drush command without the --include attribute but then my command does not know where the STARTERKIT folder is.
Here is where I'm using the --include option to locate the STARTERKIT folder.