Installs into .claude/skills of the current project.
Are you the author of Regulatory Updates?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/bromso-regulatory-updates)
---
description: Track and assess impact of new or changing regulations
---
# 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