what-the

Explain technical concepts using who, what, where, why, and when framing.

92.8k|8.2k|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/thedotmack/claude-mem --skill what-the
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: what-the
Source: https://github.com/thedotmack/claude-mem/tree/main/plugin/skills/what-the
Command: npx skills add https://github.com/thedotmack/claude-mem --skill what-the

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical jargon and complex systems often leave users confused about the basics. This Skill breaks down any technical topic into a plain-English narrative covering the people involved, the thing being discussed, the location or context, the reasoning behind it, and the timing.

Core Features & Use Cases

  • Plain-English Breakdown: Translates dense technical material into accessible language using the classic five Ws framework.
  • Universal Applicability: Works for any technical subject — code, infrastructure, protocols, frameworks, or processes.
  • Use Case: A new engineer joins a team and asks about the deployment pipeline. Use this Skill to get a clear explanation of who owns it, what each stage does, where it runs, why the architecture was chosen, and when each step triggers.

Quick Start

Use the what-the skill to explain the who, what, where, why, and when of Kubernetes ingress controllers.

Frequently Asked Questions about what-the

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explain a technical concept to a non-technical audience?

Use the five Ws framework — who, what, where, why, and when — to structure your explanation. Start with the people or systems involved, describe the core mechanism, locate where it operates, justify its existence, and place it on a timeline.

What is the best way to break down complex systems simply?

Anchor the explanation in concrete actors and events rather than abstractions. Identify the primary participants, the core action, the environment, the motivation, and the sequence of occurrences to make any system comprehensible.

Does this approach work for explaining code architecture?

Yes. Map the five Ws to architectural elements: who are the services or modules, what is the core responsibility, where does data flow, why was the pattern chosen, and when does each component activate during execution.

When should I avoid using the five Ws breakdown?

Avoid it when the audience already needs deep technical precision, such as API reference documentation or low-level implementation guides. The framework prioritizes accessibility over exhaustive detail.