# Improving Writing Culture

> Use when setting team writing standards, designing document templates, fixing a review process, or diagnosing why an organization's documents are consistently unclear.

- Skill: `introvenk/improving-writing-culture` (Agent Skill)
- Install (CLI): `npx skillmds@latest add introvenk/improving-writing-culture`
- Raw SKILL.md: https://api.skillmd.com/api/skills/introvenk/improving-writing-culture/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: introvenk (https://skillmd.com/u/introvenk)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/introvenk/improving-writing-culture

---


# Improving Writing Culture

## Overview
Bad writing is usually a symptom of a team's system, not any one author's skill. This skill addresses the system: templates, review processes, and what leadership models — not any single document.

## Why bullshit accumulates
- **Lost editorial filters** — nobody's job is to cut a document down before it ships.
- **Volume** — more documents, less time per document, more copy-paste of prior bad examples.
- **Fear** — hedging and vagueness are often a rational response to a culture where directness gets punished.

## Writing reveals culture
Passive-voice incident reports ("mistakes were made") usually mean nobody feels safe stating what happened plainly. Treat a pattern of vague writing across a team as a signal to investigate the underlying safety, not just a style problem to fix document-by-document.

## Leadership modeling
People imitate what they see from leadership. A leader who hedges bad news in their own updates cannot expect direct status updates from their reports.

## Interventions
- **Question reviewer lists.** Remove reviewers who don't materially improve a document — they add latency and dilution, not editorial value.
- **Rewrite templates that institutionalize vagueness** — a mandatory "executive summary" section nobody reads teaches authors to pad.
- **Reward uncomfortable clarity** — visibly credit the postmortem that names a real cause, not the one that spreads blame thin.

## Change sequence
Generate awareness → share knowledge → build support systems. Don't try to fix a team's writing culture by fiat in one meeting — each stage needs the previous one to hold.

## Recruit allies
Find people with influence who already write well and want better documents from others. Change spreads faster through peers than through a top-down mandate.

Human-practice material (protected writing time, focus conditions) is context for the user, not agent-actionable instruction — a skill can't enforce "get 90 uninterrupted minutes."