A variation on @Eric Ringold's solution. This example BESTEST OSW just gives you a look at pre-made OSW files that are still run with the CLI. These are JSON files you can make and edit with any text editor. Note the name, description, and modeler description fields for each measure are optional. they won't impact how it functions. It is important that if you have EnergyPlus measures they appear after OpenStudio Measures, and that reporting measures appear after any EnergyPlus measures. After you run the OSW with the CLI, an overloaded copy of the input OSW will be created with measure logs that contain info, warning, and register value statements.
This repositoryhas a more complex approach but may be useful. All BCL measures are also in GitHub.com as Ruby gems. This rake tasks installs the gems that contains the measures and updates the measure paths in the OSW. This is a way to keep a repository very light weight (without any measures) but still easy to test and update.
