Follow the shared workflow in ../wps-learning-workflow.md.
Inputs
- A WPS study note or topic that currently feels difficult
- An old WPS note that may cover foundational knowledge
- Optional course stage, exam context, or difficulty description
Output
A structured WPS-ready prerequisite knowledge gap report, including missing foundations, a repair path, and self-test items after completion.
What this skill should produce
The goal is not just to tell the user "there is a gap here," but to further explain: what is missing, why they are stuck, what to fill in first, and how to verify after filling it in.
It is recommended to include these sections:
required prerequisitescovered in existing notesmissing or weakwhy this blocks understandingrepair planself-check after repair
WPS-first rules
- If the old notes already contain content that can fill the foundation, clearly point out the corresponding note title.
- If there are no old notes to review, say so directly; do not make things up.
- Break the repair plan into small actions as much as possible, and give an approximate amount of effort.
Quality rules
- Divide the gaps into three tiers: blocker, important but recoverable, and optional depth.
- Focus more on the foundations that "block understanding," rather than listing all related background in one go.
- The gap explanation should be directly tied to the current topic, so the user knows why they are stuck here.
This skill should identify prerequisite gaps, not diagnose all misunderstandings in the current note.
Do not use when
- What the user wants to find is an error or misunderstanding within the current note.
- The topic itself is already mostly understood; they only need to extract review highlights.
- The current topic scope is too scattered to form a meaningful prerequisite chain.
Recommended next skill
Usually recommend:
misconception-finderstudy-note-linker