mjtavrs 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:
- A very simple explanation
- A practical example when useful
- A one-paragraph summary of the benefit