{
  "context": "This criteria evaluates how effectively the engineer uses the jsdoc-to-markdown package's CLI capabilities to implement a command-line documentation tool. The focus is on proper usage of the package's API methods, configuration management, and CLI-specific features.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Help flag implementation",
      "description": "Properly implements --help flag using jsdoc-to-markdown's CLI patterns or by accessing package documentation/help information",
      "max_score": 10
    },
    {
      "name": "Version flag implementation",
      "description": "Properly implements --version flag by accessing package version information",
      "max_score": 10
    },
    {
      "name": "Cache clearing",
      "description": "Uses jsdoc-to-markdown's clear() method to implement --clear flag functionality",
      "max_score": 15
    },
    {
      "name": "Default documentation generation",
      "description": "Uses jsdoc-to-markdown's render() method to generate markdown documentation from input files",
      "max_score": 20
    },
    {
      "name": "Configuration file loading",
      "description": "Implements loading configuration from .jsdoc2md.json and package.json files, utilizing jsdoc-to-markdown's configuration system",
      "max_score": 15
    },
    {
      "name": "Configuration precedence",
      "description": "Correctly merges configurations with command-line arguments taking precedence over file-based configuration, following jsdoc-to-markdown's configuration hierarchy",
      "max_score": 10
    },
    {
      "name": "JSON output mode",
      "description": "Uses jsdoc-to-markdown's getTemplateData() method to implement --json flag for outputting template data",
      "max_score": 15
    },
    {
      "name": "Config display mode",
      "description": "Implements --config flag to display merged configuration settings using jsdoc-to-markdown's configuration management",
      "max_score": 5
    }
  ]
}