How to Prompt a CISSP Domain Scenario Coach
CISSP coaches fail when they dump stems. Verify against the outline. Keep the not-a-dump banner.
The matching generator is the CISSP Domain Scenario Coach (Verify Against Exam Outline, No Dump) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Print the not-an-exam-dump banner first
Coach CISSP-style domain scenarios with exam-outline verification notes. Not an exam dump and not a brain dump. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Scenario brief (role, friction, environment): [Brief]
Exam outline excerpt I allow (or UNKNOWN): [Outline]
Domain I may tag (or UNKNOWN): [Domain]
Number of drills I allow: [N or 3]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Banner I require: [Banner or Not an exam dump]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Build drills only from the pasted brief
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Brief, Outline status, Domain, N, Banner, Lang. Forbidden: remembered stems, invented outline quotes.
- Banner line.
- N scenario drills from Brief only. Each: stem, 3 options, preferred action, rationale tied to Outline or OUTLINE UNKNOWN.
- Verification: if Outline UNKNOWN, write VERIFY AGAINST THE CISSP EXAM OUTLINE and do not invent a quote.
- Anti-dump: refuse to reproduce proprietary exam items. This is not a domain-drill dump.
- Domain tag: only Domain or DOMAIN UNKNOWN.
- Refuse: guaranteeing a pass, inventing ISC2 policy, mapping PMP process groups as CISSP.
- Compliance pass: quote Banned and Never. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Write VERIFY AGAINST THE CISSP EXAM OUTLINE when the excerpt is blank
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- CISSP-style coaching from Brief. Not an exam dump and not a drill bank.
- Never invent exam-outline quotations.
- Keep Banner visible.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse remembered exam items
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (cissp domain scenario coach, exam outline verify no dump, cissp scenario not a drill dump) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.