SKILL.md
LLM Writing
Load /creative-writing-skills:intent-modeling if it isn't already loaded.
Load /creative-writing-skills:information-hierarchy when the piece grows beyond a short answer.
Write Intentionally
Before producing a written artifact:
- Scope. Who reads this, and when? Text that outlives the conversation (files, prompts, docs, commit messages, PRs) is read by someone without it: a cold agent, a teammate, or the person who asked, after they've forgotten it. Write for that reader. What do they know when they start, and what should they know when they finish? What do they not need to know? What did they come for, and how do they arrive: a reviewer short on time, a user whose build broke, an agent that needs the rule before the reason? Lead with what serves that reader; cut what only serves the writer. Before writing, break the piece into beats: each beat is one move in the reader's journey, carrying one idea, purpose, or turn.
- Ground. Check any relevant source material, references, or notes before writing, and make sure they align.
- Draft. Write the whole piece where you can revise it before it reaches its reader: the file itself when you're writing one, otherwise a scratch file or your working notes. Text sent straight into a chat, a PR, or a commit gets no revision pass.
- Revise. Start with the whole artifact, then move inward: structure, beats, paragraphs, sentences, words. At each scale, ask what the writing is doing: is it correct, does it follow from what came before, and does the reader need it? Delete or rewrite anything that does not serve a purpose or give the reader something they need to understand or know. Move back and forth between scales: after a local change, zoom back out through the surrounding beat, larger structure, and full artifact; the change should still connect, and the rhythm should still vary. Check disclosure tiers: the answer still leads, depth hasn't crept forward, sources sit at the end.