anchor.diff:  
   Opskeleton generates the complete folder structure for projects:
   
  -image:https://raw.githubusercontent.com/opskeleton/opskeleton/master/img/puppet-layout.png[width=40%,hight=50%]
  -
  -==== module lifecycle
  +image:https://raw.githubusercontent.com/opskeleton/opskeleton/master/img/puppet-layout.png[width=30%,hight=50%]
  +
  +==== lifecycle
   
   Opskelaton defines a module life cycle:
   
  
positive.code:  
  Opskeleton comes to solve these issues by introducing a decentralized development work flow with pre-defined layout, packaging and dependency management.
  
  
  == Usage
  
  Currently Opskeleton supports Puppet and Chef, this guide is segmented to common functionality the respective separate sections for Puppet and Chef.
  
  === Installation
  
negative.code: 
  An external node classifier based runner is also available under scripts/run.sh, this runner expects to get a <hostname>.yaml input file with the required node classes.
  
  === Updating
  Keeping you box up to date with latest opsk version is easy, just re-generate it again and resolve conflicts by answering y/n:
  ```bash
  