--- name: writing-with-ai-checks description: 15 rules from the Noesa course "AI for writing at work". For professionals writing emails, summaries, updates, and documents with AI — faster, still in their own voice, and saying only what they've checked. --- # AI for writing at work — the rules Use with: Claude Code or Claude (save as a skill), Cursor (save under .cursor/rules as .mdc), ChatGPT or any other assistant (paste the text below into custom instructions or a project's instructions). 15 rules, taken from the course at https://noesa.leafsoft.online/c/writing-with-ai Each heading is one thing the course teaches. Most are checks to run on your own output before presenting it as done; a few are background you are expected to have. "Wrong by default" lists 6 specific ones. Apply these to the thing you are producing — the type, the schema, the query, the copy — not only to how you explain it. Where a rule names a field, a format or an identifier, that name belongs in the output. ## Write the brief before the draft Write a four-line brief that gives an AI draft a clear reader, purpose, set of key points, and tone. ## Keep your voice Identify the recurring traits in your writing, supply useful samples, and run a de-blanding pass on an AI draft. ## Draft the everyday email Use a sixty-second workflow to draft a clear request, update, or reminder and keep ownership of its facts and action. ## Handle the hard email Use AI to explore hard-email options while keeping the decision, accountability, and final words with yourself. ## Summarize a meeting honestly Produce a meeting summary that distinguishes decisions, actions, discussion, and unresolved questions against the source. **Wrong by default:** - A leaning with a condition attached, and then explicitly parked, is not a decision — and writing it as one manufactures an authority nobody in the room exercised. Keep decisions, conditions and parked items on separate lines, so a preference waiting on someone else cannot be read as settled. - One person in the discussion objected, on a concrete cost, and the summary reports agreement instead. A summary that drops the only dissent removes the thing a reader most needed to see, and nothing else in the document carries it. Record who disagreed and on what grounds, even when the majority leaned the other way. - Nobody assigned it. Saying a plan works for you is agreement, not an owner accepting a task, and a summariser that converts one into the other attaches a real name to work that person never took on. An action line needs someone who actually said they would do it. ## Turn notes into a status update Transform scattered work notes into a status update organized around progress, evidence, risks, decisions, and next actions. ## Write for the reader above you Write a bottom-line-first one-pager that gives an executive the decision, evidence, trade-off, and next step without hiding uncertainty. ## Draft the customer-facing words Draft a customer-facing article or support macro that is clear, accurate, appropriately warm, and bounded by approved policy. ## Build documents outline-first Create and test an outline, draft one section at a time, and keep a longer workplace document coherent. ## Edit with AI, don't be edited by it Run separate tightening and clarity passes, evaluate suggested changes, and reject edits that alter meaning or voice. ## Say it three ways Adapt one set of confirmed facts for customers, restaurant partners, and colleagues while preserving a single source of truth. ## Check the writing before it ships Run a stakes-matched pre-send check over names, numbers, dates, claims, promises, links, and actions. **Wrong by default:** - A draft that states a total in one sentence and promises a further refundable item in the next has committed to the sum of both — here 48.60 plus a 4.99 fee, so 53.59, not the 48.60 it repeats twice. Total every promise the text makes rather than trusting the figure it states most often; the customer will reconcile it against their statement. - 19 March 2026 is a Thursday; the Friday is the 20th. A weekday and a date sitting in one phrase are two separate claims, and a draft that gets one right can still get the other wrong. Check both. - It is a commitment in your name to a date you do not control. Check any timing promise against what the payment process actually guarantees, and soften it to what you can stand behind if it does not. ## Keep it honest and yours Decide when AI assistance should be disclosed, document material contributions, and take accountable authorship of the final writing. ## Build your voice kit Assemble, test, and trim a Voice kit that guides AI-assisted writing from brief through final check. ## Ship a real piece end to end Use your Voice kit to produce, verify, and release one real workplace document while recording the decisions you retained.