When I first saw this topic, I was not sure but now I have an idea of how I would use it.
Project documentation - how website should look and work is now described in PDF document. Asana tasks duplicate this info for developers by breaking it down. For example how Homepage should look & work is described both in PDF document and also in Asana "Homepage" task. Duplication is not good of course, sync issues, etc. So, maybe that document could be generated by your module.
That case would need to work with custom fields too. For example, I might have 50+ tasks, but only 10 of them are actual Epics (large tasks) - Homepage, My Account, etc. I only need them to be generated in document.
What do you think about this case?