Suggested Workflow

While working on a new header-only library from this skeleton (gzip), wasn't completely sure how we want to suggest creating a separate library when using this skeleton as a foundation. This ticket is also relevant to the workflow we'll want to suggest when using node-cpp-skel.

### Possibilities
- Fork: If we suggesting forking, there should be a easy way to remove skel's github history to start from scratch and create a completely separate copy with its own history.
- Branch: There would be no intention of merging custom code/a separate lib into master, so this doesnt seem like the right way to go.
- ?

I'll do a bit more research on how other projects/developers have done this.

cc @springmeyer @mapsam

No files, tests, or entry points are named. Review the fork and branch possibilities described in the issue and the current repository workflow, then document a decided approach for creating a separate header-only library with its own history; done means the recommended workflow and cleanup steps are clear.

Written by the indexing model from the issue text.