title: custom grunt task naming convention
body: <p>Is there any convention regarding naming custom grunt tasks that include more than one word? For example: <a href="https://github.com/werk85/grunt-json-schema" rel="noreferrer">grunt-json-schema</a> grunt plugin has <a href="https://github.com/werk85/grunt-json-schema/blob/master/tasks/json_schema.js" rel="noreferrer"><code>json_schema</code> task</a>. One name includes dashes (<code>-</code>), the other includes underscores (<code>_</code>).</p>
  
  <p>Obviously, dashed-name can't be used as a JavaScript object key:</p>
  
  <pre><code>grunt.initConfig({
      json-schema: { // WON'T work
  </code></pre>
  
  <p>they have to be enclosed in quotes:</p>
  
  <pre><code>grunt.initConfig({
      'json-schema': { // will work
  </code></pre>
  
  <p>I checked all official plugins (<code>grunt-contrib-*</code>), but they all consist of only one word. The motivation foor this question is simple: I just want to follow conventions.</p>