# Regulatory Tracking

> Track regulatory changes — jurisdiction monitoring, impact assessment, compliance gap analysis, implementation planning, and stakeholder notification. TRIGGER when: user says /regulatory-tracking, needs to monitor regulatory changes, or asks about staying compliant with evolving regulations.

- Skill: `ashutoshsrivastava17/regulatory-tracking` (Agent Skill)
- Install (CLI): `npx skillmds@latest add ashutoshsrivastava17/regulatory-tracking`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ashutoshsrivastava17/regulatory-tracking/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: ashutoshsrivastava17 (https://skillmd.com/u/ashutoshsrivastava17)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ashutoshsrivastava17/regulatory-tracking

---

# Regulatory Tracking

> **Disclaimer:** Not legal advice. Consult qualified legal counsel for compliance decisions.

## Process
### Step 1: Identify Regulatory Landscape
| Jurisdiction | Regulations | Authority |
|-------------|-----------|-----------|
| Federal | [Applicable regulations] | [Agency] |
| State/Province | [Applicable regulations] | [Agency] |
| International | [GDPR, etc.] | [Authority] |
| Industry | [Sector-specific] | [Body] |
### Step 2: Monitor Changes
| Source | Frequency | Method |
|--------|-----------|--------|
| Federal registers | Daily | RSS/alerts |
| Regulatory agency sites | Weekly | Manual review |
| Legal newsletters | Weekly | Email subscription |
| Industry associations | Monthly | Member updates |
| Legal counsel updates | As needed | Advisory |
### Step 3: Assess Impact
| Change | Affected Areas | Severity | Deadline |
|--------|---------------|----------|----------|
| [regulation] | [departments/processes] | H/M/L | [date] |
### Step 4: Plan Implementation
| Action | Owner | Timeline | Status |
|--------|-------|----------|--------|
| Policy update | Legal | [date] | ☐ |
| Process change | Operations | [date] | ☐ |
| Training | HR/L&D | [date] | ☐ |
| System update | IT | [date] | ☐ |
### Step 5: Notify Stakeholders
| Stakeholder | Communication | Timing |
|------------|--------------|--------|
| Executive team | Impact brief | Within 1 week |
| Affected teams | Implementation plan | Within 2 weeks |
| All employees | Policy update | Before effective date |
## Output Format
```markdown
## Regulatory Update: [Regulation]
### Change: [Summary]
### Impact: [Affected areas and severity]
### Timeline: [Effective date and milestones]
### Actions: [Implementation plan]
```
## Quality Checklist
- [ ] All relevant jurisdictions monitored
- [ ] Impact assessment completed for each change
- [ ] Implementation timeline meets compliance deadlines
- [ ] Stakeholders notified appropriately
- [ ] Legal counsel reviewed assessment
## Edge Cases
- For cross-border operations, track overlapping regulations
- If deadlines conflict, prioritize by penalty severity
- For ambiguous regulations, document interpretation rationale