writing-skills

Use this skill whenever you are writing or updating technical documentation: a README, an install guide, setup or config docs, dev docs, API docs, help text, a troubleshooting section, and also every commit message and pull request description. Trigger on "write a README", "document this", "update the install guide", "our docs are out of date", "write the commit message", "open a PR", or "write the PR description". It edits the file directly, and it verifies every path, command, and flag against the actual code before writing about them. This is technical writing: transactional prose, no author's voice to preserve. Do NOT use it for writing that has a voice: essays, blog posts, emails, marketing copy, anything persuasive or personal. Those belong to the `draft` plugin. Do not use it to ghostwrite something new from nothing; it documents systems that already exist.

Use this skill whenever someone wants feedback on a piece of writing without committing to changing it: essays, emails, board policies, internal docs, marketing copy, blog posts, or any prose draft. Trigger on phrases like "critique this", "how does this read?", "what's wrong with this", "give me notes on this", "review this draft", "does this land", "get me a second opinion on this", or "/critique [file]". This is a read-only pass — it never edits the file. If the user wants the writing actually fixed, not just assessed, use `tighten` instead.

Use this skill whenever someone hands you a piece of writing and wants it actually fixed: tightened, cut for economy, given a rigorous line edit. Essays, emails, board policies, internal docs, marketing copy, blog posts, or any prose draft. Applies every edit automatically, no approval step (at most a one-line calibration question on a long doc whose purpose is ambiguous) — the right call whenever the ask is "just make this better" and the user doesn't want to review each change. Trigger on phrases like "tighten this", "clean this up", "fix this", "edit this for economy", "make this leaner", "cut the fluff from this doc", "give this a line edit and apply it", "this feels bloated, fix it", or "/tighten [file]". Works on a single document or a batch in one run: several board policies, a folder of drafts, a stack of emails. If the user wants feedback without the file being changed, use `critique` instead. Don't reach for this when the request is to write something new, brainstorm, or restructure unprompted; it e

Simulates a page-one editorial meeting on a pitch or idea: a dynamic panel of editor personas debates it live via SendMessage, then delivers a verdict. Trigger on "page one meeting", "run this by the editors", "simulate a pitch meeting", "editorial meeting on this", "get the room's take", "workshop this with a panel of editors", or /page-one-meeting. For a single quick editorial read instead of a multi-agent debate, use the managing-editor agent directly, not this skill.

Runs a pitch through a single managing-editor read instead of the full page-one-meeting panel: one Socratic verdict (green light / revise / kill), no cast, no debate, no dissent round. Trigger on "sharpen this pitch", "sharpen my pitch", "quick editorial read", "give me an editor's take", "run this by an editor", or /sharpen. For a full multi-persona debate instead, use the page-one-meeting skill.