Review Proposals

anthropics/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.

410 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

8996

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/anthropics/claude-for-legal --skill review-proposals

The instruction itself

3 sections, as written by the author

/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.md before 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)

How to use it

Copy the folder

Take anthropics/review-proposals from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.