First pass at a great workflow RFC to rule them all.

Yeah, but if you've got one big PolicyFile and named run_lists in them, how does that exactly work? 

I think dan is going towards a world where your app stacks would still have per-app PolicyFile's which would have the dev/int/test run_lists in them -- you'd just manage them in one big chef-repo.   That's more interesting to me, since its getting to the question of how many PolicyFile's you have and where they go in the repo (which then drives the generators that you need, etc).

I can also see people slightly flipping out over having multiple PolicyFiles scattered around their cookbooks, so I think its worth nailing down the use case so that we can address any Berksfile trauma here.