anchor.diff:  }
   ----
   
  -For more detail, see the https://picocli.info/#execute[Executing Commands] section of the user manual.+For more details, see the https://picocli.info/#execute[Executing Commands] section of the user manual.
positive.code: 
  Similar to the annotation API, `OptionSpec` objects have `help`, `usageHelp` and `versionHelp` attributes. When the parser matches an option that was marked with any of these attributes, it will no longer validate that all required arguments exist. See the section below on the `parseWithHandler(s)` methods that automatically print help when requested.
  
  === `PositionalParamSpec`
  
  `PositionalParamSpec` objects don’t have names, but have an index range instead. A single `PositionalParamSpec` object can capture multiple positional parameters. The default index range is set to `0..*` (all indices). A command may have multiple `PositionalParamSpec` objects to capture positional parameters at different index ranges. This can be useful if positional parameters at different index ranges have different data types.
  
  
negative.code: public class ProgrammaticCommand {
  
      public static void main(String[] args) {
          CommandSpec spec = CommandSpec.create(); // <1>
          spec.mixinStandardHelpOptions(true); // usageHelp and versionHelp options
          spec.addOption(OptionSpec.builder("-c", "--count")
                  .paramLabel("COUNT")
                  .type(int.class)
                  .description("number of times to execute").build()); // <2>
          spec.addPositional(PositionalParamSpec.builder()
                  .paramLabel("FILES")
                  .type(List.class).auxiliaryTypes(File.class) // List<File>
                  .description("The files to process").build()); // <3>
          CommandLine commandLine = new CommandLine(spec);
  
          // set an execution strategy (the run(ParseResult) method) that will be called
  