Status of project

I see great value to cpp-cli-skel because:

- Command line interfaces are a great way to prototype new projects
- Command line interfaces are a common and very valuable way to distribute C++ code, and therefore establishing best practices for how Mapbox devs develop C++ CLI interfaces is important for scaling our work.

At the same time this project has been dormant, in my mind, because:

- Attention of @mapbox/core-tech has so far been primarily on https://github.com/mapbox/hpp-skel
- https://github.com/mapbox/hpp-skel, because it contains benchmarks and unit tests executables, already has two types of "cli" examples, and therefore is fairly useful for using to prototype (no need for this separate cpp-cli-skel)
- Most serious command line tools end up needing to parse options, and option parsing in C++ requires an external dependency, which raises the harder question of which external dependency, refs https://github.com/mapbox/cpp/issues/35

Questions in my mind:

- Should we put this project on ICE and clearly direct interested people to hpp-skel for prototyping for now?
- Should we put time into investigating the ideal option parser and reboot https://github.com/mapbox/cpp-cli-skel/pull/2 with it and get things landed and working?

@mapbox/core-tech

Start by reviewing hpp-skel's existing CLI examples, the unresolved option-parser discussion in mapbox/cpp#35, and the proposed cpp-cli-skel#2 pull request. Determine whether this project should be paused or rebooted; done means the maintainers have chosen and documented a clear direction.

Written by the indexing model from the issue text.