Only possible after issue #6 when multiple Docufy implementations are added,

Allow extracting which Docufy to use based on output checklist file extension, or a command line flag to force a specific implementation.

An XML version of Docufy.

Also, a default implementation of XSLT to turn the result into an HTML.

While the command line parameter allows specifying directories to scan, it would be nice to also allow it to also parse specific files.

The command should support the -- flag, which signals all subsequent command line parameters are files (i.e., anything parameter afterward that starts with a - will be part of a filename.

Right now the DocufyText has support for exporting compact checklists. This (compacting) should instead be a native docufy parameter which should have a command line parameter to control.

README to allow users to know how the heck to do anything with the program.

There's a command line option, --impl <impl_name> to specify which implementation to use.

But, there's no obvious way to know what impl_names are possible. Request for a command line that lists the supported implementations.

An implementation to create a Markdown checklist, with

• these
  and

formatted

header

sections

All IDs should be unique, even IF they have different groups or subgroups.

The output (for DocufyText) should alert users of id collisions in the parsed content.

Right now, the entire process of scanning a directory is pretty silent.

It should have more content shown to the console,

• to show the user it's active
• to show the current action it took
• to show a general sense of progress