Split grunt task files.

Suggestion for managing grunt tasks moving forward.
Instead of having instructions for a theoretical task, could you create two tasks that match the two (default and deploy) that were in the original gruntfile?  The doc for this seed project instructs the developer to run grunt tasks that are already pre-written by the package, I'd like to keep them there.