| name | cissp-recap |
| description | End-of-session debrief — summarize what was studied, surface new weak spots, offer to write to kb/ |
Produce an end-of-session debrief for the user.
Steps
-
Look at the current conversation for what was studied this session:
- Domains touched
- Topics explained / quizzed / drilled
- Questions the user got wrong
- Concepts they asked follow-up questions on (signal of curiosity OR confusion)
-
Cross-reference with webapp/data/progress.json for any quiz attempts logged during this session.
-
Render the debrief:
SESSION DEBRIEF — <today's date>
───────────────────────────────
WHAT YOU STUDIED
- <domain / topic> — <1-line takeaway>
- ...
WHAT YOU GOT WRONG (or got slowly)
- <topic> — <one-sentence on the misconception>
- ...
PATTERNS I NOTICED
<1-3 sentences. Things like "you keep mixing X and Y" or "your sysadmin instincts are pulling you toward technical answers when ISC2 wants the management answer first">
SUGGESTED FOR kb/
- A note for `kb/domain-notes/dN-<slug>.md` capturing <topic> in your own words
- Update `kb/weak-areas.md` with: <topic>, <topic>
NEXT SESSION
<one-line specific recommendation>
- Offer concrete write-back actions, one at a time. Ask the user before writing:
- "Want me to update
kb/weak-areas.md with the topics above?"
- "Want me to draft a note at
kb/domain-notes/dN-<slug>.md?"
- "Want me to log this session to
kb/session-log.md for spaced review later?"
Rules
- Only debrief what actually happened this session. Do not fabricate accomplishments.
- If the session was light (e.g., user only asked 1-2 questions), say so and skip the debrief — recommend they do a
/quiz-me or /cissp-explain first.
- The output writes to
kb/, never wiki/. The wiki is canonical; kb/ is personal.
- No emoji. The user is tired by now — keep it tight.