$ loading_
Review open NPRM comment periods, log decisions, track deadlines. Use when an NPRM has a comment window open and you need to surface deadlines, decide whether to file, or record a filing / not-filing / waived decision (--decide CMT-ID).
复制安装指令，让 AI 自动完成配置 · 推荐新手
请帮我安装 askskill 上的 "comments" 技能： 1. 下载 https://raw.githubusercontent.com/anthropics/claude-for-legal/main/regulatory-legal/skills/comments/SKILL.md 2. 保存为 ~/.claude/skills/comments/SKILL.md 3. 装好后重载技能，告诉我可以用了
NPRMs have deadlines. The decision to file a comment or not is an attorney call — but the deadline disappearing without a logged decision is the risk. This skill surfaces open comment periods and records decisions.
~/.claude/plugins/config/claude-for-legal/regulatory-legal/comment-tracker.yaml → all tracked NPRMs and their status.
~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md → default comment decision owner.
## Comment Period Tracker — [date]
### ⏰ Deadline in <14 days
| ID | Regulation | Deadline | Days left | Decision | Owner |
|---|---|---|---|---|---|
| CMT-001 | [name] | [date] | [N] | Undecided | [owner] |
### 🟡 Open (>14 days)
[same table]
### Recently decided
| ID | Regulation | Decision | Rationale |
|---|---|---|---|
| CMT-002 | [name] | Not filing | [reason] |
---
**Total open:** [N] **Undecided with deadline <30 days:** [N]
/regulatory-legal:comments --decide CMT-001
Decision: [filing / not-filing / waived]
Rationale: "[brief — e.g., 'Rule doesn't apply to our model' or 'Filing comment on Section 3']"
Updates tracker. If decision is "filing": prompt for filing deadline reminder (comment deadline minus 5 business days for internal review).
On first detection of an NPRM (populated by reg-feed-watcher): Slack DM to
comment decision owner if Slack MCP is configured and owner_slack is set.
Reminder at 14 days before deadline if decision is still "undecided." Reminder at 3 days before deadline if still undecided — elevated urgency.
Before logging a decision as "filing" — and always before producing a comment letter or regulator-response draft for submission: Read ## Who's using this in ~/.claude/plugins/config/claude-for-legal/regulatory-legal/CLAUDE.md. If the Role is Non-lawyer:
Submitting a comment or response to a regulator has legal consequences. It's a public statement of the company's position, it's on the record in the rulemaking or enforcement matter, and positions taken here bind the company and can be used against it in subsequent proceedings. Have you reviewed this with an attorney? If yes, proceed. If no, here's a brief to bring to them:
- The rulemaking or inquiry (regulator, docket, deadline)
- What the proposed comment/response says and on what sections
- Open questions and what's unresolved
- What could go wrong (adverse admissions, inconsistent prior positions, coordination-of-comment concerns with trade associations)
- What to ask the attorney (should we file at all; should we file jointly through a trade group; are there positions we should not take)
If you need to find a lawyer: your professional regulator's referral service is the fastest starting point (state bar in the US; SRA/Bar Standards Board in England & Wales; Law Society in Scotland/NI/Ireland/Canada/Australia; or your jurisdiction's equivalent).
Do not log a "filing" decision or produce a submission-ready draft past this gate without an explicit yes. Tracking views, deadline reminders, and "not-filing / waived" decisions do not require the gate.
/regulatory-legal:reg-feed-watcher.The
comment-decisiongap_typesemantics, the per-send Slack confirmation rule, and the comment-tracker.yaml schema live in the gap-surfacer reference skill — load it before doing substantive work.
Review and approve (or reject) pending playbook update proposals from the playbook-monitor agent and apply approved changes to the practice profile. Use when the playbook-monitor agent has surfaced proposals, when the user says "review playbook proposals", "what playbook updates are pending", or wants to step through deviation-driven playbook changes.
Reference: review of SaaS subscription agreements with attention to the terms that matter most in subscription deals — auto-renewal mechanics, price escalation, data portability, uptime SLAs, and subprocessor rights. Loaded by /commercial-legal:review when a SaaS or subscription agreement is detected.
Drafts board or committee meeting minutes in your house format. Auto-detects upcoming board and committee meetings from your calendar, asks for the agenda and any slides or pre-read materials, and produces a complete draft in the format learned from your seed minutes. Also handles written consents in lieu of meetings. Trigger: "board minutes", "draft minutes", "upcoming board meeting", "committee minutes", "written consent", or calendar detection of an upcoming board or committee event.
Aggregate diligence findings into a deal team briefing at the right altitude for the audience — exec summary for leadership, working summary for the team. Use when user says "brief the deal team", "what's the state of diligence", "summarize findings for [audience]", "deal update", or on the briefing cadence.
Entity compliance tracker — initialize, report upcoming deadlines, update status, run health audit, export to CSV. Maintains a compliance-tracker.yaml built from the entity table, calculates filing deadlines by entity and jurisdiction, and surfaces what's due in the next 30/60/90 days. Use when user says "entity compliance", "filing deadlines", "annual reports due", "entity tracker", "what filings are due", "entity health", or "good standing".
Trace how a contract has changed across its base agreement and all amendments — either a summary of all changes over time, or a provision trace for a specific clause. Use when the user says "what changed in this contract over time", "show me the amendment history", "where's the latest [clause]", "how has [provision] evolved", or uploads multiple versions of an agreement.