{
  "context": "This evaluation assesses how well the engineer uses the commander package to implement command-line flag parsing and related CLI functionality. The focus is on proper use of commander's API for argument parsing, option definition, help generation, and program configuration.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Commander initialization",
      "description": "Uses commander.Command or commander.program to create the CLI application instance",
      "max_score": 10
    },
    {
      "name": "Option definitions",
      "description": "Uses .option() method to define command-line flags with both short and long forms (e.g., '-c, --config <path>', '-f, --format <format>')",
      "max_score": 20
    },
    {
      "name": "Option default values",
      "description": "Specifies default values for options using commander's default value parameter in .option() (e.g., .option('-c, --config <path>', 'description', 'config.json'))",
      "max_score": 15
    },
    {
      "name": "Argument parsing",
      "description": "Uses .parse() method to parse command-line arguments from process.argv or provided array",
      "max_score": 10
    },
    {
      "name": "Accessing parsed options",
      "description": "Retrieves parsed option values using .opts() method or property access on the program instance",
      "max_score": 10
    },
    {
      "name": "Help configuration",
      "description": "Configures help text using .description(), .usage(), or relies on commander's automatic help generation via --help flag",
      "max_score": 15
    },
    {
      "name": "Program metadata",
      "description": "Uses commander methods like .name(), .version(), or .description() to set program metadata",
      "max_score": 10
    },
    {
      "name": "Action handling",
      "description": "Uses .action() callback or checks parsed options to implement conditional logic based on flags",
      "max_score": 10
    }
  ]
}