Regulatory watch

Skill bromso/metapowers/plugins/compliance/skills/regulatory-watch

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-watch

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 regulatory changes and assess impact

SKILL.md

3.0 KB, as published. Nobody here has run it

Regulatory Watch

Track regulatory changes relevant to "$ARGUMENTS" and assess their impact on the organization's compliance posture, controls, and policies.

Prerequisites

Read .metapowers/compliance/$ARGUMENTS/00-scope.md. If this file does not exist, tell the user:

Phase 0 (Scope) has not been completed for "$ARGUMENTS". Run /compliance:regulatory-landscape $ARGUMENTS first, or use --skip-checks to bypass.

If --skip-checks is present in $ARGUMENTS, skip this check.

Process

Read context files:
- Read plugins/compliance/shared/grc-lifecycle-guide.md for GRC methodology reference
- Read .metapowers/compliance/$ARGUMENTS/00-scope.md for scope and applicable regulations
- Read .metapowers/compliance/$ARGUMENTS/04-monitor.md for current monitoring status
Identify regulatory changes:
- Use WebSearch to identify recent and upcoming regulatory changes relevant to the organization
- Search for amendments, new guidance, enforcement actions, and industry interpretations
- Check regulatory body announcements (EU, NIST, AICPA, ISO, sector-specific bodies)
- Review industry association publications and legal advisory updates
Impact assessment per change:
- Summarize the change — what is new, modified, or removed
- Effective date — when does compliance become mandatory
- Impact classification — new requirements, modified requirements, removed requirements
- Determine if current controls/policies need updating
- Identify new controls or evidence that may be required
- Estimate remediation effort (days/weeks/months)
Action planning:
- For each impactful change: assign owner, set implementation deadline
- Prioritize by effective date and organizational impact
- Identify changes that affect multiple regulations simultaneously
- Flag changes requiring legal review or board approval
Monitoring sources recommendation:
- Recommend regulatory body newsletters and RSS feeds
- Industry associations with compliance updates
- Legal advisors specializing in relevant regulations
- GRC vendor regulatory update services
- Peer industry groups and compliance communities
Write the artifact to .metapowers/compliance/$ARGUMENTS/04-monitor.md (append to existing) with sections:
- Regulatory Change Log — table of identified changes with effective dates
- Impact Assessments — per-change analysis of organizational impact
- Action Items — required changes to controls, policies, or evidence
- Monitoring Sources — recommended sources for ongoing regulatory intelligence
- Review Cadence — recommended frequency for regulatory watch reviews

Output

The regulatory watch report appended to .metapowers/compliance/$ARGUMENTS/04-monitor.md. Present a summary to the user highlighting:

Number of regulatory changes identified
High-impact changes requiring immediate action
Upcoming effective dates within 6 months
Recommended monitoring sources