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

This feels a bit like a pedantic detail that isn't helping me see the forest for the trees.  There's a lot of text here that basically says that we'll have a standard one-bit-chef-repo layout with some `chef generate` commands to help building it.  The generators aren't so interesting.  The workflow when you make a change to an existing cookbook and then push it to the chef server and git is more interesting (the knife-spork area, which is more than just simply uploading a cookbooks).  Then dealing with upstream cookbooks and tracking/forking them (knife vendor).  Then how you promote cookbooks to prod in a PolicyFile world, and what your PolicyFiles look like and what commands operate on them.