policy-drafter
Draft an internal policy people can actually follow — the rule stated plainly with its reason, the bright lines separated from the judgment zones, the edge cases resolved by principle, and the enforcement reality stated honestly. Use when asked write our expense/remote-work/AI-use/security policy, turn this incident into a policy, our policy doc is unreadable, or people keep asking what's allowed. Produces the policy with rules-plus-reasons, the bright-line/judgment split, the worked edge cases, and the honest enforcement section.
npx skills add mohitagw15856/pm-claude-skills --skill policy-drafter --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Policy Drafter Skill Internal policies fail readers two ways: legalese nobody parses (so folklore governs instead), or vague aspiration ("use good judgment with expenses") that answers no actual question. A followable policy states each rule plainly *with its reason* (reasons recruit compliance and guide the unlisted cases), separates bright lines (never/always, no judgment) from judgment zones (factors + who decides), and works three real edge cases in the text — because the edge cases are what people actually come to a policy to resolve. Honesty requirement: the enforcement section describes what actually happens, not theater. ## What This Skill Produces - **The policy** — scope, the rules with reasons, bright lines vs. judgment zones marked - **The worked edge cases** — 3–5 real scenarios resolved in the text, showing the principle in motion - **The enforcement section** — what happens on violation, honestly, and who decides gray cases - **The one-page summary** — the rules card people will actually consult (the full policy is the reference; the card is the interface) ## Required Inputs Ask for these if not provided: - **The behavior being governed and why now** — the incident
- What This Skill Produces
- Required Inputs
- Framework: The Followability Rules
- Output Format
- Why This Policy Exists
- The Rules (with reasons)
- Worked Edge Cases
- Enforcement (honestly)
- The One-Page Card
- Quality Checks
- Anti-Patterns
What does the policy-drafter skill do?
Draft an internal policy people can actually follow — the rule stated plainly with its reason, the bright lines separated from the judgment zones, the edge cases resolved by principle, and the enforcement reality stated honestly. Use when asked write our expense/remote-work/AI-use/security policy, turn this incident into a policy, our policy doc is unreadable, or people keep asking what's allowed. Produces the policy with rules-plus-reasons, the bright-line/judgment split, the worked edge cases, and the honest enforcement section.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill policy-drafter --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.