RAG Architecture Review Skill

A RAG system that "hallucinates sometimes" is almost never one bug — it's a chain where the weakest stage caps quality, and the symptom (a wrong answer) is far from the cause (a chunk that was never retrieved). This skill reviews an existing pipeline stage by stage, isolates where quality leaks, and ranks fixes by impact so you work the biggest lever first. (Designing a new system from scratch? Use rag-design-doc.)

Working from a brief

Given a partial description ("it uses pgvector and sometimes makes things up"), deliver the full staged review anyway — infer the likely setup for each unstated stage, label the inference, and flag what to confirm. Never withhold the review for missing detail; a labelled assumption plus "confirm this" beats a blank.

Required Inputs

Ask for these only if they aren't already provided (else infer and label):