{
  "context": "This criteria evaluates how effectively the engineer uses jsdoc-to-markdown's file input processing capabilities to handle different input sources (file paths, glob patterns, and raw source code) when building a documentation generator CLI.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses render method",
      "description": "Correctly imports and uses the main `render()` method from jsdoc-to-markdown to generate markdown documentation",
      "max_score": 20
    },
    {
      "name": "Single file input",
      "description": "Passes single file paths to jsdoc-to-markdown using the `files` option, e.g., `render({ files: 'path/to/file.js' })`",
      "max_score": 15
    },
    {
      "name": "Multiple file input",
      "description": "Passes multiple file paths to jsdoc-to-markdown using an array in the `files` option, e.g., `render({ files: ['file1.js', 'file2.js'] })`",
      "max_score": 15
    },
    {
      "name": "Glob pattern input",
      "description": "Passes glob patterns to jsdoc-to-markdown using the `files` option with wildcard patterns, e.g., `render({ files: 'lib/**/*.js' })`",
      "max_score": 20
    },
    {
      "name": "Raw source code",
      "description": "Passes raw JavaScript code strings to jsdoc-to-markdown using the `source` option, e.g., `render({ source: 'function foo() {}' })`",
      "max_score": 20
    },
    {
      "name": "Correct option names",
      "description": "Uses the correct jsdoc-to-markdown option names (`files` for file paths/globs, `source` for raw code) rather than inventing custom options",
      "max_score": 10
    }
  ]
}