plugins/pm-gov/skills/regulatory-impact-analysis/SKILL.md
Produce a regulatory impact analysis (RIA) weighing the costs, benefits, and alternatives of a proposed rule. Use when asked to assess a regulation's impact, do a cost-benefit analysis of a policy, justify a rulemaking, or compare regulatory options. Produces a structured RIA: the problem and rationale, options including the baseline, costs vs. benefits, distributional effects, and a reasoned recommendation.
npx skillsauth add mohitagw15856/pm-claude-skills regulatory-impact-analysisInstall 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.
Before a rule is made, good practice (and often law) requires showing it's justified: what problem it solves, what it costs, what it delivers, and whether a lighter option would do better. This skill produces a structured RIA — honest about uncertainty, comparing real alternatives against the do-nothing baseline.
Educational analytical aid. A formal RIA must follow the jurisdiction's guidance (e.g. US OMB Circular A-4, UK Better Regulation Framework) and use validated data — treat this as a rigorous first draft, not an official filing.
Ask for these only if they aren't already provided:
1. Problem statement & rationale — the specific problem (market failure, externality, risk) and why intervention is needed now. If there's no clear problem, say so.
2. Objectives — what success looks like, in measurable terms.
3. Options considered — including the baseline (do nothing) and non-regulatory alternatives. Describe each.
4. Costs & benefits by option — for each option, the expected costs and benefits (quantified where possible; qualitative where not), over the timeframe. A comparison table:
| Option | Key costs | Key benefits | Net assessment | |---|---|---|---|
State assumptions, data sources, and uncertainty honestly (ranges, sensitivity).
5. Distributional effects — who gains and who bears the costs (small business, regions, groups); any equity concerns.
6. Recommendation — the preferred option and why it's proportionate — the best net benefit for the burden imposed.
7. Implementation & review — enforcement, compliance burden, and how/when the rule's effect will be evaluated (sunset/review clause).
Regulatory impact analysis practice (OMB Circular A-4 / Better Regulation): problem-first, options vs. baseline, cost-benefit, proportionality.
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.