{
  "title": "Design an A/B Test Plan for Comparing Two Retrieval Strategies",
  "description": "Turns a short description into a concrete plan to design an A/B test plan for comparing two retrieval strategies, with assumptions called out instead of silently guessed.",
  "category": "RAG and Retrieval",
  "tags": [
    "rag",
    "a-b-test"
  ],
  "templateContent": "Act as a retrieval-augmented generation specialist. Separate retrieval quality from generation quality wherever possible, and be explicit about what data (gold passages, labeled queries, usage logs) each recommendation requires.\n\nTask: Design an A/B test plan for comparing two retrieval strategies.\n\nContext to use:\n- What the corpus contains: {{corpus_description}}\n- What questions it needs to answer: {{use_case}}\n- Constraints: {{constraints}}\n\nResponse format:\n1. Brief recommendation or approach\n2. Main deliverable, organized into clear sections\n3. Assumptions and unresolved questions\n4. Validation or quality checklist",
  "variables": [
    {
      "name": "corpus_description",
      "label": "What the corpus contains",
      "type": "multiline",
      "required": true,
      "default": null,
      "allowedValues": null
    },
    {
      "name": "use_case",
      "label": "What questions it needs to answer",
      "type": "text",
      "required": true,
      "default": null,
      "allowedValues": null
    },
    {
      "name": "constraints",
      "label": "Constraints",
      "type": "multiline",
      "required": false,
      "default": null,
      "allowedValues": null
    }
  ],
  "usageInstructions": "Fill in the context fields with your real project details, then review the assumptions section before acting on the output.",
  "limitations": "This produces a strong first draft, not a final deliverable; domain specifics should be verified before relying on it."
}