review-proposals
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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-08
- Stars
- ★ 10.0k
- Forks
- 2.0k
01 前言 Front Matter
- name
- review-proposals
- description
- 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.
- argument-hint
- [no arguments needed — works from the pending proposals file]
03 SKILL.md 正文
/review-proposals
Steps through pending playbook update proposals from the monitor agent and applies approved changes to ~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md.
Instructions
-
Load the playbook-monitor agent and run Step 5 (review and approval flow).
-
If no proposals file exists or it is empty: respond "No pending proposals. Playbook is up to date." Do not proceed further.
-
Present proposals one at a time. For each, show the full proposal block and offer four options: Accept, Reject, Edit, Defer.
-
For Accept or Edit: show the exact diff to
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.mdbefore writing. Only apply after the attorney explicitly confirms. -
For Reject or Defer: log the decision. Do not modify
~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md. -
After all proposals are resolved: show a summary of what changed, then archive the proposals file.
Examples
/commercial-legal:review-proposals
/commercial-legal:review-proposals
(runs automatically after playbook-monitor notifies you)
04 同仓库更多 Skills
reg-feed-watcher
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
policy-redraft
Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
policy-diff
Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.
matter-workspace
Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
gaps
Open gaps tracker — what's flagged and not yet closed. Use when the user asks "what gaps are open", "gap tracker", "remediation status", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.