anchor.diff:    kept in .git/scribe
   
   To Do List
  -===================
  +==========
   
       $ git scribe todo
   
  
positive.code:     * LICENSE.txt
      * README.asciidoc
      * .gitscribe
    
  Not all of those files would be generated (like the test files and the site files which are overrides for the site templates), but examples would and it would give a usable starting point for new authorship.  This example would be a valid and somewhat complex layout.
  
  
negative.code: The Dream
  =========
  
  This is where I'm documenting basically what I want the README to eventually look like.  This is sort of my Document Driven Development file.  I'm trying to envision what the git-scribe project should look like as I write the tool.  I didn't want it to be in the readme yet so as not to confuse people.  All the commands are just ideas and what not.  If you have an idea of how you would like things to look, add them here and send a pull request.
  
  I want to get the full workflows worked out here (with technical details) before I even try to implement them.
  
  Start a Book
  ============
  
      $ git scribe init (--type=[code,math]) (--license=[public,cc]) (--lang=en) [project]
  
  