# Policy in plain language

> Rewrite a policy so a resident can act on it, without changing what it means.

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

---


# Rewriting a policy for residents

The test is whether somebody can work out what to do. Not whether the summary
is accurate — accurate and unusable is the normal failure.

## Rewrite

Short sentences, active voice, everyday words, second person. Replace defined
terms with what they mean and keep the defined term in brackets once.

## Lead with the reader's question

"Am I eligible, and what do I do?" comes before purpose, scope and background.
Most policy documents are ordered for their author.

## Keep every obligation and every deadline

Simplifying is not shortening. A duty, a deadline, an exception or an appeal
right that is dropped changes the policy — and this is a rewrite, not a
revision.

## Structure

What this is about · who it applies to · what you must do, as steps · deadlines ·
what happens if you do not · how to appeal or complain · who to contact.

## Never

Resolve an ambiguity in the source by choosing a reading — flag it. Never soften
a consequence.