plugins/pm-gov/skills/policy-memo/SKILL.md
Write a decision-ready policy memo that frames an issue and recommends an option. Use when asked to write a policy memo, options paper, decision memo for a principal/minister/executive, or brief a decision-maker on a policy choice. Produces a tight memo: the issue, background, options with trade-offs, a clear recommendation, and implementation/risks — written for a busy decision-maker who reads the first paragraph.
npx skillsauth add mohitagw15856/pm-claude-skills policy-memoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A policy memo exists to drive a decision, not to demonstrate research. The decision-maker reads the top and wants: what's the issue, what are my realistic options, what do you recommend, and what happens if I say yes. This skill writes that — BLUF (bottom line up front), honest options with trade-offs, and a defensible recommendation.
Ask for these only if they aren't already provided:
To / From / Date / Re — standard header.
Bottom line (BLUF) — 2–3 sentences: the issue, your recommended option, and the key reason. A busy reader should get the decision from this alone.
Issue — the precise question to be decided, and why it needs a decision now.
Background — only what's needed to decide (concise; detail goes to an annex). Facts, constraints, what's at stake.
Options — 2–4 realistic options (including status quo). For each: what it is, pros, cons, cost/feasibility, and who's affected. A comparison table helps:
| Option | Pros | Cons | Cost / feasibility | |---|---|---|---|
Recommendation — the option you recommend and why it best fits the goals and constraints. Be decisive; acknowledge the main trade-off you're accepting.
Implementation & risks — key steps, timeline, who does what, and the main risks + mitigations.
Next step / decision requested — exactly what you're asking the reader to approve.
Government & executive decision-memo practice (BLUF, options analysis, evidence-based recommendation, implementation).
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.