Policy Document Drafter

Policies that are unclear or unwritten create inconsistent decisions, unfairness, and risk. This skill drafts an internal policy that states the rule, the reasoning, and the how, in plain language people will actually read and follow, without the dense legalese that gets ignored. Clear policy is how a growing team stays fair and consistent without a manager adjudicating everything.

1. The policy topic and why it is needed.
2. The rules or expectations to set.
3. Who it applies to and any exceptions.
4. How it is enforced and who owns it.
5. Any legal or compliance requirements to reflect (from the user).

1. State the purpose and scope plainly

Why the policy exists and who it applies to, up front. People follow rules they understand the reason for.

2. Write the policy in plain language

The actual expectations, stated clearly and specifically. Avoid legalese and vague words like "appropriate" without defining them, since vagueness pushes the judgment call back onto every reader.

3. Cover the how, not just the rule

The procedure to comply (how to request, report, or act), so the policy is usable, not just declarative.

4. Address exceptions and edge cases

Where the rule flexes, who approves exceptions, and what to do in the gray areas people will actually hit.

5. Set enforcement and ownership

The consequences of non-compliance, who owns the policy, and when it is reviewed, so it stays current and is applied consistently.

ALWAYS use:

# Policy: [Topic]
## Purpose
## Scope (who it applies to)
## Policy (the rules, plainly stated)
## Procedures (how to comply)
## Exceptions and approvals
## Enforcement
## Owner and review date

• Legalese no employee will read.
• Vague terms like "appropriate" left undefined.
• Rules with no procedure for how to comply.
• No owner or review date, so the policy goes stale.

This drafts internal policy language; it is not legal advice. Where a policy touches employment law, safety, privacy, or regulated areas, recommend review by qualified counsel or HR before adoption, and flag the parts that likely need it.

An AI-use policy states its purpose, defines approved and prohibited tools plainly, gives the procedure for requesting a new tool, names the exceptions process, and flags data-handling clauses for legal review.