Write the PR description

Write for a reviewer who has not read the conversation. Follow the repository's template. Lead with the concrete problem and resulting behavior; use a trigger and before/after example when it clarifies the change. Read the relevant GLOSSARY.md under the configured agent root for domain terms.

Load plain-english and deslop-written through the Skill tool when available; otherwise read their SKILL.md files. Describe the final diff. Omit conversational history and abandoned approaches unless they explain a consequential tradeoff.

Explain and show the change

Use the smallest amount of prose that makes the change reviewable. A simple fix often needs one or two sentences plus validation.

Add a visual when it explains ownership, order, state, or data flow more clearly than those sentences:

• Pseudocode for an algorithm or condition.
• A call tree for runtime order.
• A shallow file or component tree for responsibility.
• A small diff sketch for changed behavior within a familiar shape.
• Mermaid for interactions across components or processes.
• Before/after screenshots for a visual change, with the relevant state visible.