Home/Blog/How to Prompt a CISSP Domain Scenario Coach from an Outline
Blog

How to Prompt a CISSP Domain Scenario Coach from an Outline

P
promptstudio
How to Prompt a CISSP Domain Scenario Coach from an Outline

Scenario coaches dump live stems. Anchor every item to the outline.

The matching generator is the CISSP Domain Scenario Coach from a Pasted 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).

Map outline headings as anchors

Coach CISSP-style scenarios from a pasted domain outline. Verify against the outline. Never dump exam questions from memory. 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:

Pasted domain outline / objectives: [Outline]
Domain label I lock: [Domain]
Number of scenarios: [Count]
Difficulty I lock: [Difficulty]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Sources I may cite (exact list or NONE): [Sources]

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.

Label PRACTICE NOT LIVE EXAM

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:

  1. Honesty ledger: Outline headings count, Domain, Count, Difficulty, Sources status, Lang. Forbidden: remembered exam dumps, invented official item IDs.
  2. Outline map: headings used as anchors.
  3. Scenarios: Count items. Each has stem, 4 options, correct letter, rationale tied to an Outline heading. Label PRACTICE NOT LIVE EXAM.
  4. Anchor list: each scenario -> Outline heading quote.
  5. Refuse list: verbatim recalled ISC2 items, answer keys from dumps, invented official form numbers.
  6. Diff notes: Banned/Never cuts.
  7. Not-advice banner: not a certification guarantee; not employer advice.
  8. Compliance pass: Banned/Never hits. Scenario count. Gaps list of five. 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.

Refuse invented ISC2 item IDs

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 practice from Outline only. Not CompTIA and not a dump.
  • Never invent official item IDs or dump remembered stems.
  • Mark PRACTICE NOT LIVE EXAM.
  • 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.

Keep the not-advice banner

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 scenario coach, no exam dump, cissp domain outline) 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.