review-proposals

To review playbook updates, surface pending proposals one at a time, evaluate the generated diff for your CLAUDE.md file, and explicitly confirm acceptance before any changes are written. Rejected or deferred items leave the practice profile untouched.

The safest way to approve playbook changes is using a diff-first, write-after-confirmation process that shows exact modifications to the practice profile before applying them. Non-accepted outcomes are logged and proposals are archived after resolution.

Yes, you can edit or defer a playbook update proposal during the review cycle. The workflow supports Accept, Reject, Edit, and Defer decisions for each queued proposal block, ensuring only solicitor-approved updates modify your practice profile.

Yes, a pending proposals file must exist to start reviewing commercial legal playbook changes. The workflow checks for this file to surface queued proposal blocks that require explicit confirmation gating before any writes are applied to the practice profile.

Audit logging records non-accepted outcomes when rejecting or deferring playbook proposals. The workflow logs these decisions, leaves the CLAUDE.md practice profile untouched, and archives the proposals file after all pending updates are fully resolved.

The best way to manage outdated commercial legal guidance is through a controlled review of proposed playbook changes. This process evaluates pending update proposals individually, applies only solicitor-approved modifications, and archives rejected or deferred items to maintain profile accuracy.