swarm-writelisted

# swarm-write — writing for humans Most agent-written copy fails the same way: no voice, even rhythm, filler detail, and the machinery showing through. This skill is not a banned-word filter. Filters date fast and flatten every voice into one texture. Write from a stance, then subtract. ## Jurisdiction (check this first) | lane | reader | what applies | |---|---|---| | **end-user text** | humans who did not ask for it | all of this skill | | agent-facing (prompts, tickets, queue, skill files) | models | machine lane, unchanged | | project docs (SRS, ADRs, specs) | owner + future agents | clear and complete, no voice work, no marketing | | code and the prose inside it | engineers | §Code lane only | Outside the first row, stop reading and write as you normally would. ## 1. Name the reader before writing a word One line, not an interview: **who reads this, what they do next, what they already know, what makes them quit.** Most agent copy is bad because it was written for whoever asked, not whoever reads. Write to **one person**, not an audience. "A backend dev at a 20-person startup who just got paged" produces sharper prose than "developers," every time. Specificity in the reader creates specificity in the writing. ## 2. Voice **First: whose voice is it?** The surface decides, and getting this wrong personalizes what shouldn't be personal: - **Personal** (the user's posts, portfolio, personal brand, a project that *is* them) → the user's voice. Profile, menu candid