1---2name: writing-artifacts3description: Draft and revise external writing such as Medium articles, GitHub issues, pull requests, technical docs, release notes, and user-facing copy. Use only when explicitly invoked for paste-ready writing with a defined audience, format, tone, or acceptance criteria.4---56# Writing Artifacts78## Brief910- Identify audience, purpose, reader action, format, tone, length, and source constraints.11- If a missing choice would change the result, ask. Otherwise choose a plain, useful default.12- Treat supplied facts, links, code, names, dates, and examples as source truth. Mark unknowns; do not invent them.13- Honor the artifact's requested length. Do not force the chat reply word cap onto a paste-ready deliverable.1415## Format branches1617### Medium article1819- Open with the reader's problem, promise, or a concrete story. Earn attention quickly.20- State one clear thesis. Give each section one job, with examples or evidence that move it forward.21- Use a useful title, readable headings, specific transitions, and a conclusion that leaves the reader with a decision or next step.22- Remove sales language, generic lessons, fake certainty, and filler introductions.2324### GitHub issue2526- Title = the observable problem or requested outcome.27- Structure = summary + context + steps to reproduce + expected behavior + actual behavior + evidence + scope + acceptance criteria.28- Preserve exact errors, paths, commands, versions, dates, and links. Separate facts from hypotheses.29- Report one coherent problem. Include a proposed fix only when requested or clearly useful.3031### Pull request3233- Structure = what changed + why + user or system impact + proof run + risk or rollout notes.34- Link the issue or decision when supplied. State known gaps and follow-up work without hiding it in prose.3536### Docs, notes, and copy3738- Describe the accepted current state, not the editing history.39- Match the reader's job: explain, decide, perform, or understand. Use headings, examples, and calls to action only when they help.4041## Final pass4243- Check audience, purpose, structure, claims, links, code, dates, length, and requested tone.44- Remove repetition, chatbot filler, inflated claims, unexplained jargon, and process commentary.45- Return the finished artifact first. Add a short note only when the user asks for explanation or a material gap needs attention.
sgaabdu4