scope-change-controller-scott-margetts

Generate draft OOS entries and client communications from scope-change signals.

630|79|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill scope-change-controller-scott-margetts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scope-change-controller-scott-margetts
Source: https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/scope-change-controller-scott-margetts
Command: npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill scope-change-controller-scott-margetts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the capture of scope-change signals across legal matters by generating draft OOS entries, summaries, and client-ready communications, reducing manual overhead and protecting billable value.

Core Features & Use Cases

  • Automatic identification of scope signals from matter communications (emails, notes) and generation of draft scope entries.
  • Production of client-facing drafts and internal OOS documentation to support quick, collaborative decision-making.
  • Baseline extraction and management of the scope baseline, with optional escalation to full scope registers for complex matters.

Quick Start

Provide the engagement letter and a change request to generate a draft OOS entry and client notification.

Frequently Asked Questions about scope-change-controller-scott-margetts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate out-of-scope change requests for legal matters?

To automate out-of-scope change requests, you can use this skill to automatically identify scope signals from matter communications and generate draft OOS entries. It produces client-ready drafts and internal documentation to support quick decision-making.

What is an out-of-scope register and how does it help with matter management?

An out-of-scope register tracks scope changes across legal matters to protect billable value. This skill generates these registers by capturing scope-change signals from notes and emails, creating reproducible risk notes and baseline scope summaries for ongoing matter management.

How do I generate client communications for a scope change request?

You generate client communications for a scope change request by providing the engagement letter and the specific change request. The skill then drafts client-facing notifications and internal OOS documentation to facilitate collaborative decision-making.

Can I extract a baseline scope summary from an existing engagement letter?

Yes, you can extract a baseline scope summary from an engagement letter. The skill performs baseline extraction and management of the scope baseline, with optional escalation to full scope registers for complex legal matters.

Does this approach support retrospective analysis of scope changes?

Yes, this approach supports retrospective analysis of scope changes. It applies to matter setup, ongoing change requests, and retrospective analysis by producing reproducible outputs like OOS registers, risk notes, and standard scope summaries.