Hire an AI client scope change planner

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A scope comparison: original scope against the requested change, with clause references
• The effect on your team's hours and on work already promised
• Two or three delivery options, each with cost and date effects you can support
• A draft decision brief for the client, with open questions and approval status
• A list of what you could not verify, such as a missing clause

How it does the job well

• Start from the user problem and the evidence for it, then the solution.
• Write decisions down with the reason and the options you rejected.
• Keep scope small enough to ship and learn. Name what is out of scope.
• Define how success will be measured before building.

Mistakes it avoids

• Saying a change is in scope when the clause is unclear.
• Quoting a cost or date you cannot trace.
• Writing the draft as if the client had agreed.
• Treating opinions or one loud request as proven demand.
• Specs that skip edge cases, error states or dependencies.
• Roadmaps with dates but no owners or confidence levels.

What a good result looks like

An example, not your task: A client emails "can you also do this?" in the middle of a project.

• Scope comparison. Each deliverable and exclusion, the requested change, and whether it is in, out or unclear, with clause references.
• Change rules. How your contract says changes are approved, plus fee and notice terms.
• Team effect. Hours needed against hours free, and which promised work moves or slips.
• Options. Two or three ways to respond, each with the cost and date effects you can support.
• Decision draft. A client-ready brief with the options, open questions and approval status. Not sent.
• MISSING and CHECKS MISSED. Clauses or figures you did not supply, and any check that could not run.

How the work is checked

• Original and proposed commitments stay separate. The client has not accepted a change until evidence shows it.
• No cost or date appears in an option without a source or an ASSUMED label.
• The draft is not sent, and the brief says so. This is not legal advice.
• Every fact, figure and date traces to a source or is labeled as an assumption.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

Capabilities

• Plain-words contract summary. Reads the signed engagement and finds the deliverables, exclusions, change procedure, fees and notice terms, each with a clause reference. Hands step 2 the baseline scope and the change rules. Check before moving on: every line cites a clause or says it is not covered.
• Team capacity planner. Sets the request against your team's real commitments, skills, effort ranges and free hours. Shows what moves or slips in work already promised. Hands step 3 the effect on hours and dates. Check before moving on: estimates are labeled as given or assumed.
• Stakeholder update writer. Drafts the client decision brief: the options, the cost and date effects you can support, open questions and approval status. The draft is not sent. Hand-back check: the original scope and the proposed change stay separate.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id prepare-a-client-scope-change-brief only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/prepare-a-client-scope-change-brief/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• The signed engagement: contract, proposal or statement of work
• The client's change request, as they wrote it (email, message or notes)
• Your current commitments and dates for the team
• Effort evidence: your estimates or time on similar past work
• Hours your people have free, and who must approve a change on your side

Helpful context (optional)

• The original proposal and any earlier change notes.
• A named person who approves changes on your side.

Tools and access

• A chat AI that reads files: It can quote the contract by clause, so the comparison rests on the document and not on memory.
• Your time tracking or project tool: Past hours on similar work make effort estimates something you can support.
• Any good chat AI: A one-message prompt works in any strong chat AI, with nothing to install.
• Any good chat AI: It needs your numbers pasted in. A tracker or calendar connection saves typing.
• Any good chat AI: It only needs your notes pasted in. A tracker connection is a bonus, not a need.

Functions and deliverables

• Client scope change planner: Share the signed scope, change request and available hours. Get a scope comparison, delivery options and a client decision draft.
  • A scope comparison: original scope against the requested change, with clause references
  • The effect on your team's hours and on work already promised
  • Two or three delivery options, each with cost and date effects you can support
  • A draft decision brief for the client, with open questions and approval status
  • A list of what you could not verify, such as a missing clause
• Contract plain-language summary writer: Share a contract and say which side you are on. Get a short summary of duties, money, exit terms and clauses to question.
  • A summary under 300 words
  • Clauses to watch, with section numbers
  • What is vague or missing
  • Questions to ask the other side
• Team capacity planner: Give it your team and projects. Get workload against people, who is overloaded, and whether you can take on more.
  • A table of hours available, hours used and percent full for each person
  • A list of who is over or under their target
  • Which coming projects fit and which leave a gap
  • Three to five options with the hours each one frees up
  • One recommendation, and what would change it
  • A list of assumptions and missing facts
  Source: Anthropic.
• Stakeholder update writer: Turn your rough progress notes into a weekly, monthly or launch update for leaders, engineers, partners or customers, sized to the reader.
  • A draft update sized to your reader, ready to paste
  • A status colour with a one-line reason
  • Each risk with a plan or an owner
  • Each decision with options and a recommendation
  • A list of facts you still need to add
  • A version for a second reader (optional)
  Source: Anthropic.
• Product context file writer: Share product facts, audience and positioning. Get a reviewed context file that other marketing skills can reference.
  • A product marketing context file
  • A summary of what the file already holds
  • A change log of updates
  • Gaps you still need to fill
  Source: Corey Haines.

Tasks you can use it for

• A client emails "can you also do this?" in the middle of a project.
• A request sounds small but touches work already promised to someone else.
• You suspect a request is outside the contract and need to show where.
• A client wants the same date for more work and you have to say what gives.

Limits to check before starting

• The client already signed the change. Plan the hours with the Team capacity planner.
• You need a lawyer's view on what the contract means, or a dispute is under way. This workflow gives no legal advice.
• You only want a plain summary of the contract. Use the Contract plain-language summary writer.
• The change is a priced variation on a building job. Use the Construction change decision brief writer workflow.
• The request is for a whole new project. Use the Client project kickoff planner workflow.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Open Claude, ChatGPT or Gemini. Pick one that can read files, since you will attach a contract.
• Add the workflow pack. Attach the signed engagement and the client's request, then paste your commitments, effort estimates and free hours.
• After step 1, check the clause references against your own copy. Fix any line the AI cannot point to a clause for.
• After step 2, check the hours with whoever runs delivery. If an estimate is a guess, mark it as one.
• Send the decision draft to the account owner for review first. It goes to the client only after a person approves it.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/prepare-a-client-scope-change-brief for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.