Individual skill

rag-design-doc

Design a Retrieval-Augmented Generation system end to end. Use when asked to design a RAG pipeline, a 'chat with your docs' feature, a knowledge assistant, or to debug why a RAG system gives wrong/ungrounded answers. Produces a RAG design doc — ingestion & chunking, embeddings & index, retrieval & reranking, the generation prompt, grounding/citations, evaluation, and failure modes with mitigations.

plugins/pm-ai/skills/rag-design-doc/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,536
Repository last updated
Nov 8, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# RAG Design Doc Skill

Most RAG systems fail not at generation but at retrieval — the model answers confidently from the
wrong chunks. This skill forces the decisions that actually determine quality (chunking, retrieval,
reranking, grounding) and pairs each with how you'll evaluate it, so "it hallucinates sometimes"
becomes a diagnosable, fixable pipeline.

## Required Inputs

Ask for these only if they aren't already provided:

- **Corpus** — what's being retrieved over (docs, tickets, code, tables), size, and update frequency.
- **Queries** — the kinds of questions users ask, and how precise/recall-sensitive they are.
- **Grounding requirement** — must answers cite sources? Is "I don't know" acceptable (it should be)?
Back to top