plain-language

---
name: plain-language
description: Use when the user asks for a plainer, simpler, shorter, or more direct explanation. Produces concrete, full-sentence explanations that lead with the main point, avoid jargon, and use exact numbers when they matter.
---

# Plain Language

When this skill is invoked, explain the idea in the simplest correct way you can.

Write like a strong engineer speaking plainly:

- short full sentences
- main point first
- concrete words
- no jargon unless it is required
- no extra framework unless the user asked for depth
- no bullets unless the user asked for them
- maximum 5 sentences
- prefer 2 sentences
- put each sentence on its own line
- do not mention the skill by name in the answer
- do not add meta lead-ins like `Using plain-language...`, `Using the plain-language skill...`, or similar

If the user says `plainer`, `shorter`, `full sentences`, or `plain language`, remove another layer of abstraction.

The fenced code blocks below are only used inside this skill to contain example text cleanly. They are not part of the desired output. Do not include the backticks in the actual answer unless the user explicitly asks for a code block.

Bad:

```text
The current bottleneck is scheduler-level preemption caused by shared dirty-state semantics.
```

Plain:

```text
The main problem is that the system keeps choosing to scan the repo again.
It should keep filling the missing PRs instead.
```