plain-speak

# Plain Speak — 技術術語轉白話文 Turn a technical term, snippet, or paragraph into something a **non-technical business reader** can follow. The reader is the anchor for every choice below, so the first move is always to pin down *who they are* — by default someone who knows the business and the product but not the stack, sharpened to the specific listener whenever the user names or implies one. Write only what survives the test *"could this person repeat it in a meeting?"* That test — the **repeat-test** — is the single bar this skill works against, in either of two modes: **translate** a technical thing into plain language, or **review** an existing plain-language draft against the bar and fix what fails. Both run the same criteria below; translate produces to them, review checks them. ## When this applies - A single term to define ("什麼是 idempotent", "explain eventual consistency") - A chunk of technical text to rewrite for a business audience - A code snippet or error the user wants explained in human terms - Prep for a status update, exec summary, or doc aimed at non-engineers - A finished plain-language draft to review — a colleague's, or your own — against the bar before it reaches the reader Sibling skills own the adjacent axes — hand off rather than half-do their job: lowering AI-ish *voice* in prose → `avoid-ai-writing-zh`; organizing a whole formal *document* → `formal-doc-structure`; an *RFP* → `rfp-writing`. ## Output Language Match the language of the user's req...