writing-to-userslisted

# Writing to Users One person wrote to us. This skill is how we write back. It covers every one-to-one reply: a comment on a GitHub issue, the receipt and shipped emails, a decline, an answer in a discussion, a reply on Discord or social media. It builds on `writing-for-humans`, which owns everything published for everyone (docs, changelog, UI copy). Read that first if you have not. This skill adds what a reply to a specific person needs: the standard in `meta/user-care.md`, the three reply shapes, and the checks before anything posts. ## When to use - Someone opened a GitHub issue or discussion and has not been answered - A feedback report needs its receipt, decision, or shipped note - We are declining a request or closing a report - Any time a named person is waiting on us Do not use it for a changelog entry, release notes, or a docs page. That is `writing-for-humans` and `writing-changelogs`. ## The three replies Every report gets these three, in order, per `meta/user-care.md`. Each one is short. Each one names something real. ### 1. Heard (within one business day) Four parts, in this order, usually four to six sentences total: 1. Their name and thanks. "Thanks, Karl." 2. One specific detail from their report that proves a person read it. Quote or paraphrase something only their report contains. 3. What we are doing right now. "I've filed it and I'm reading through the log you attached." 4. When they hear next. A day, not "soon." Example: > Thanks, Karl. The pa