# Plain Language Explainer

> Use this skill whenever code changes are made and a simple explanation is needed for someone non-technical, outside IT, or even a child.

- Skill: `mjtavrs/plain-language-explainer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mjtavrs/plain-language-explainer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mjtavrs/plain-language-explainer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mjtavrs (https://skillmd.com/u/mjtavrs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mjtavrs/plain-language-explainer

---


# Plain Language Explainer

## Goal
Explain technical changes in a very simple, friendly, concrete way.

## When to use
Use this skill after any meaningful change:
- new feature
- bug fix
- refactor
- security improvement
- schema change
- UI change
- API adjustment

## Audience
Explain as if talking to:
- a non-technical stakeholder
- someone outside IT
- or a child

## Explanation rules
- avoid jargon when possible
- if a technical term is unavoidable, explain it simply
- say what changed
- say why it changed
- say what problem it solves
- say what practical effect the user or team will notice
- keep it concrete and easy to visualize

## Preferred structure
- What we changed
- Why we changed it
- What gets better now

## Tone
- simple
- clear
- calm
- direct
- never patronizing

## Do not
- overload the explanation with internal implementation details
- use acronyms without explanation
- assume technical knowledge
- write long, dense paragraphs

## Output format
Always provide:
1. A very simple explanation
2. A practical example when useful
3. A one-paragraph summary of the benefit