{
  "skill_name": "ai-documents-validation-document-type",
  "eval_focus": [
    "repo-specific-document-type-workflow",
    "diagnostic-contract-preservation",
    "api-consumer-integration",
    "correct-routing-to-analyst-docs-reviewer-or-orchestrator"
  ],
  "evals": [
    {
      "id": 1,
      "prompt": "Aggiungi supporto al certificato camerale in E:\\ai-documents-validation.",
      "expected_output": "Uses this skill, reads AGENTS.md, follows docs-first policy, and plans/implements all document-type surfaces instead of only classification.",
      "expectations": [
        "Mentions project_path discovery and ai_documents_validation_docs",
        "Includes config, parser, router, rules, reliability, API catalog, CLI, tests, and docs",
        "Requires field diagnostics for each expected field"
      ]
    },
    {
      "id": 2,
      "prompt": "Modifica solo REFERENCE_TEXTS per riconoscere un nuovo documento nel validatore.",
      "expected_output": "Flags classification-only change as an anti-pattern and requires full pipeline alignment.",
      "expectations": [
        "Rejects or challenges the incomplete scope",
        "Explains parser/rules/reliability/API/test/doc gaps",
        "Keeps legacy behavior unless explicitly changed"
      ]
    },
    {
      "id": 3,
      "prompt": "Reviewa questo diff: aggiunge un parser documento ma non produce field_diagnostics.",
      "expected_output": "Finds a blocking domain issue using the diagnostic contract.",
      "expectations": [
        "Requires extract_<name>_fields_with_diagnostics",
        "Requires diagnostics for every expected field",
        "Mentions allowed statuses confirmed/partial/conflicting/missing"
      ]
    },
    {
      "id": 4,
      "prompt": "Indicizza la documentazione del progetto ai-documents-validation nello shelf docs.",
      "expected_output": "Routes to mcp-docs-navigator as primary skill, not this skill.",
      "expectations": [
        "Recognizes pure docs maintenance",
        "Names mcp-docs-navigator",
        "Keeps this skill only as domain context if needed later"
      ]
    },
    {
      "id": 5,
      "prompt": "Parti da ticket, commit multipli e allegati PDF per capire perche' un nuovo documento fallisce in QA.",
      "expected_output": "Routes first to mcp-technical-analyst for multi-source reconstruction.",
      "expectations": [
        "Recognizes mixed evidence intake",
        "Names mcp-technical-analyst as primary",
        "Uses this skill only for subsequent document-type implementation/review"
      ]
    },
    {
      "id": 6,
      "prompt": "Integra l'API del validatore in un portale esterno.",
      "expected_output": "Uses API integration reference and covers endpoints, auth, CORS, multipart request, response contract, error handling, privacy, and consumer tests.",
      "expectations": [
        "Mentions health, supported-types, and validate endpoints",
        "Distinguishes HTTP errors from validation status KO",
        "Recommends machine-readable fields over llm_message_for_user for workflow"
      ]
    },
    {
      "id": 7,
      "prompt": "Aggiungi un nuovo tipo documento e rendilo disponibile all'app consumer.",
      "expected_output": "Includes both document-type pipeline work and API consumer exposure work.",
      "expectations": [
        "Updates API schema/catalog/supported-types as needed",
        "Updates API tests",
        "Documents any new context fields explicitly"
      ]
    },
    {
      "id": 8,
      "prompt": "Reviewa genericamente questa PR Python senza contesto documentale.",
      "expected_output": "Routes to mcp-code-reviewer rather than this skill.",
      "expectations": [
        "Recognizes generic review scope",
        "Names mcp-code-reviewer",
        "Does not force ai-documents-validation assumptions"
      ]
    }
  ]
}