| name | cissp-explain |
| description | Explain a CISSP topic calibrated to the user's background, with wiki + glossary + exam-trap cross-links |
Explain the topic: $ARGUMENTS
Steps
-
Read context (silently):
kb/my-background.md (if exists) — for calibration
wiki/glossary.md — for the canonical 1-line definition
wiki/exam-traps.md — for any trap related to the topic
- The relevant domain wiki page in
wiki/domains/dN-*.md for depth
kb/weak-areas.md (optional) — if this topic is on the user's weak list, lean harder on the trap explanation
-
Render the explanation in this structure:
TOPIC: <topic>
DOMAIN: D<n> — <domain name>
WHAT IT IS (1-2 sentences from glossary, plain language)
<...>
WHY IT MATTERS FOR THE EXAM
<2-4 bullet points, ISC2 perspective>
REAL-WORLD ANCHOR
<one analogy calibrated to user's background — sysadmin / dev / auditor / etc.>
EXAM TRAPS
<bullet list of related trap entries — quote them>
RELATED CONCEPTS
<3-5 cross-links, file paths like wiki/concepts/cryptography.md>
ISC2 MINDSET CHECK
<one line: which "best/first/most" framing ISC2 prefers for this topic>
- End with a question: ask if the user wants to (a) quiz themselves on this topic, (b) generate a kb/ note about it, or (c) move on.
Rules
- If the topic isn't in the wiki/glossary, say so honestly and offer to add it via
/cissp-wiki-update. Do NOT fabricate.
- If
kb/my-background.md doesn't exist, skip the real-world anchor section and gently mention /cissp-onboard could help.
- No emoji. Concise prose. The user is studying for a 4-hour exam — every sentence should pull weight.