agentsclimarketplace

Regulatory updates

Skill bromso/metapowers/plugins/legal/skills/regulatory-updates

A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.

Install
npx -y skills add bromso/metapowers --skill regulatory-updates

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Track and assess impact of new or changing regulations

SKILL.md

4.4 KB, as published. Nobody here has run it

Regulatory Updates

Track and assess the impact of new or changing regulations for "$ARGUMENTS". Research recent regulatory changes, assess their impact on current compliance posture, and create implementation timelines.

Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.

Prerequisites

Check that .metapowers/legal/$ARGUMENTS/00-assess.md exists. If it does not exist, stop and tell the user:

"Run an Assess skill first (e.g. /legal:risk-assessment $ARGUMENTS) to generate the prerequisite assessment artifact."

If the user passes --skip-checks, bypass this check and log the skip to .metapowers/legal/$ARGUMENTS/skip-log.md with a timestamp and the reason "Prerequisite check skipped for regulatory-updates".

Process

  1. Read inputs:

    • Read .metapowers/legal/$ARGUMENTS/00-assess.md for current regulatory landscape, jurisdiction, and compliance status
    • Review any existing compliance artifacts in .metapowers/legal/$ARGUMENTS/

  2. Research regulatory changes:

    • Use WebSearch to find recent and upcoming regulatory changes relevant to "$ARGUMENTS"
    • Focus on the jurisdictions and regulation types identified in the assessment
    • Search for proposed legislation, final rules, guidance updates, and enforcement trends
    • Check regulatory body announcements, industry association updates, and legal news sources

  3. Summarize each regulatory change:

    • What is changing — clear description of the new requirement or modification
    • Effective date — when the change takes effect or compliance is required
    • Who it affects — which teams, processes, or systems are impacted
    • What action is needed — specific steps required to comply

  4. Assess impact on current compliance:

    • Rate each change as High, Medium, or Low impact:
      • High — requires significant process changes, new controls, or substantial investment
      • Medium — requires moderate adjustments to existing processes or policies
      • Low — requires minor updates or documentation changes
    • Map each change to existing controls and identify gaps

  5. Prioritize required changes:

    • Rank by deadline urgency (nearest effective dates first)
    • Weight by impact severity (high-impact changes take priority)
    • Consider dependencies between changes
    • Flag any changes with penalties for non-compliance

  6. Create implementation timeline:

    • For each required change, define milestones and target completion dates
    • Assign responsible owners for each implementation task
    • Identify resource requirements (budget, personnel, technology)
    • Build in buffer time for review and testing

  7. Flag items requiring legal counsel review:

    • Ambiguous regulatory language requiring interpretation
    • Changes with significant financial or operational impact
    • Cross-jurisdictional conflicts or complexities
    • Novel regulatory requirements without established compliance patterns

  8. Recommend monitoring sources:

    • Regulatory bodies — official government and agency websites
    • Industry associations — sector-specific compliance organizations
    • Legal newsletters — reputable legal update services
    • Peer networks — industry working groups and compliance forums
    • Suggest monitoring frequency for each source

  9. Write the artifact to .metapowers/legal/$ARGUMENTS/04-govern.md with frontmatter:

    ---
description: Regulatory updates for $ARGUMENTS
---

    Include sections:

    • Regulatory Change Summary — table of all identified changes with status
    • Impact Assessment — detailed analysis per change with severity rating
    • Priority Matrix — changes ranked by urgency and impact
    • Implementation Timeline — milestones, owners, and target dates
    • Legal Counsel Review Items — flagged items requiring attorney input
    • Monitoring Sources — recommended sources and review frequency

Output

The regulatory updates written to .metapowers/legal/$ARGUMENTS/04-govern.md. Present a summary to the user highlighting:

  • Number of regulatory changes identified and their impact distribution
  • Most urgent changes requiring immediate action
  • Items flagged for legal counsel review
  • Recommended monitoring cadence going forward

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.