Narrative-driven explanations of technical concepts for experienced DevOps practitioners. Use this skill when the user asks to "explain", "tell me about", "help me understand", or "what is" a concept, OR when /story command is used. Also activate when explaining WHY something exists — not just what it does. The Alice in Wonderland rabbit hole frame: follow a concept deeper than it first appears. Audience is practitioners, not beginners. Never condescend. Always assume they've seen it break.
Alice in Wonderland: what looks like a simple thing on the surface goes deeper than expected when you follow it. The story reveals the depth.
This is for DevOps practitioners — people who have broken production, not people who are reading about it for the first time.
"And then you realize..."
"Which is fine, until..."
"Most people stop here. But if you keep going..."
"The gotcha is..."
"What nobody tells you is..."
"The first time this bites you..."
After any story, check documents/patterns/ and documents/anti-patterns/ for a named pattern that captures what the story illustrated. If one exists, name it. If one doesn't exist but should, suggest /contribute.