한국어
☰ Categories

Map a syllabus against your course materials

Pulls learning objectives from the syllabus and shows, unit by unit, where each is covered in your materials — and which ones are not covered at all.

CategoryUsing AI › Source-grounded AI
TagsAnalyzingTableCollege student
Prompt
I have loaded my course syllabus and my course materials as sources. Build a **coverage map** from them before I start studying.

**Step 1 — objectives from the syllabus only**
List each unit or week and the learning objectives the syllabus states for it. Quote the syllabus wording; do not add objectives it does not state.

**Step 2 — where each objective is covered**
For every objective, point to the source(s) and section that cover it. Use this table:

| Unit | Objective (syllabus wording) | Covered in (source · section) | Coverage: full / partial / none |

**Step 3 — gaps**
List objectives marked *partial* or *none*. For each, say what is missing — a definition, a worked example, a derivation — so I know what to find elsewhere.

**Step 4 — three practice questions per unit**
Write them **only from what the sources contain**. After each question, name the source section the answer is in.

**Rules**
- ***Answer only from the loaded sources.*** If something is common knowledge in the field but not in the sources, it does not count as coverage
- Do not guess the exam format or weighting unless the syllabus states it — if it does, quote it
- If the syllabus is missing or has no objectives, stop after saying so
After pasting, fill in the fields at the bottom (Course name · Exam scope (optional))

What this prompt does

Before summarizing course materials, it helps to know what they do not cover. This prompt quotes the syllabus objectives, maps each to a source section with a coverage rating, lists the gaps with what is missing, and writes practice questions answerable only from the sources.

More in this category

AI Grounding Prompt
Find where your sources disagree
Report what your sources cannot answer
Build an outline from your sources
Design questions worth asking a grounded tool