{
  "title": "Design a Strategy for Retrieval Over Code Repositories",
  "description": "Turns a short description into a concrete plan to design a strategy for retrieval over code repositories, with assumptions called out instead of silently guessed.",
  "category": "RAG and Retrieval",
  "tags": [
    "rag",
    "strategy-retrieval"
  ],
  "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 a strategy for retrieval over code repositories.\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": "Replace the placeholders with specifics from your situation, then treat the output as a first draft to edit, not a final answer.",
  "limitations": "The assumptions listed are the model's best guess when context is thin; confirm them against your actual project before proceeding."
}