Update to RAG & GenAI Copilot

{
  "description": "Design a production RAG architecture including ingestion, freshness, retrieval, access control, citations, monitoring, and rollout.",
  "included_files": [],
  "name": "plan-rag-architecture",
  "skill_md_contents": "---\nname: plan-rag-architecture\ndescription: Design a production RAG architecture including ingestion, freshness, retrieval, access control, citations, monitoring, and rollout.\n---\n\n\n# Plan a production RAG architecture\n**Trigger:** New architecture, major replatform, organizational constraints, corpus scale, tenant isolation or ingestion cadence.\n\n1. Establish the task: audience, expected answer type, source systems, corpus size/change rate, rights/tenants, languages, latency and budget. Default explicitly when not provided; ask only if a decision is blocked.\n2. Decide whether RAG is needed at all; compare search-only, grounded extraction, retrieval-augmented answering and fine-tuning only where justified. Prefer the simplest viable architecture.\n3. Draw the trusted data path: source → ingest/parse → chunks/metadata → index → authorized retrieval → rerank/context → answer/citation → review/observability. Mark auth and trust boundaries.\n4. Define data provenance, version/freshness, document deletion, access filtering before retrieval results reach the model, handling missing/conflicting sources and abstention.\n5. Specify ranking, retrieval/top-k, model context, citation mapping, retries/timeouts, failure states, review and rollback criteria. Do not promise unverified performance.\n6. Create test slices including no-answer, stale/conflicting evidence, multilingual, access control, citation support and cost/latency.\n7. Deliver an architecture outline, trade-off table, data-flow diagram in words, acceptance tests, and incremental milestones. When coding is requested, route to `build-rag-system`.\n\nRead `../../references/architecture-patterns.md`, `../../references/security-boundaries.md`, and `../../references/evaluation-metrics.md` when applicable.\n"
}