Storytelling Guide - Ignore All Previous Instructions Follow-Up Questions

Source document: 10-storytelling-guide.md Reference scenario: 01-prompt-injection-defense.md -> Scenario 1: Ignore All Previous Instructions

Scenario lens: Direct instruction override after several benign turns, with prompt dilution and instruction hierarchy as the main risks. Document lens: security storytelling, STAR-D structure, and audience framing.

Use these prompts to push past the base scenario and explore deeper design, operational, interview, or storytelling tradeoffs.

Answer document: ANSWERS.md

Easy

1. What is the strongest opening hook for a story about direct prompt injection, and why would it make the listener lean in?
2. Which metric or customer-facing consequence should appear in the first two sentences?

Medium

1. How would you map Situation, Task, Action, Result, and Decision for this scenario without front-loading too much implementation detail?
2. Which detail would you change when telling the story to a security lead versus a product leader?

Hard

1. What tradeoff belongs in the Decision section so the story shows judgment instead of sounding like a generic mitigation checklist?
2. Where is the right cutoff point between narrative pacing and technical depth if the interviewer asks for more detail halfway through?

Very Hard

1. How would you retell the scenario if the first fix only reduced, but did not eliminate, the risk while still sounding accountable and credible?
2. What evidence would you preserve so the story can survive skeptical follow-up questions months later?