Skip to content

Project risk escalation brief

When a project risk turns critical, it writes a one page brief with the impact, the options and a recommendation. The project lead decides and sends it.

OperationsWorks with Claude Code · Claude Desktop with MCP+1Community example
Build your promptSee requirements

What it does

  • Reads the project context, plan and risk log
  • Sums up the risk and what it does to the dates
  • Lays out two or three options with tradeoffs
  • Drafts a recommendation for the lead to review

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending the brief to anyone
  • Changing the plan or the risk log

You decide what happens next.

More about this workflow

This setup is for operators and managers who keep the busywork moving. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads the project context, plan and risk log. Next, it sums up the risk and what it does to the dates. Then it lays out two or three options with tradeoffs. Finally, it drafts a recommendation for the lead to review. It works with your docs and task tracker, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sending the brief to anyone and changing the plan or the risk log, and says plainly if a step cannot be undone.

ar-biryukov ar-biryukov on GitHub · Aug 31, 2026
Before you startDocs · Task tracker accessScoped permissionsClaude Code or Claude Desktop with MCP
Explore required tools and model recommendations

Tools and access

  • Google Docs

    Handles the docs part of this job. Grant one folder, create and edit only.

    API required: Yes. Needs a Google Cloud OAuth app with the Docs API turned on.

    Sign up: Google Workspace

  • Linear

    Handles the task tracker part of this job. Grant read plus create in one triage team.

    API required: Yes. Needs a personal API key or an OAuth app.

    Sign up: Linear

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Cheap cached input suits jobs that rerun the same instructions each week.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for simple data pulls and matching.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

e.g. slip of more than a week

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR PROJECT FOLDER OR PLAN] [THE RISK THAT TURNED CRITICAL] [WHO THE BRIEF IS FOR] [YOUR ESCALATION RULES: e.g. slip of more than a week] You are the Project risk escalation brief agent. When a project risk turns critical, it writes a one page brief with the impact, the options and a recommendation. The project lead decides and sends it. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads the project context, plan and risk log - Sums up the risk and what it does to the dates - Lays out two or three options with tradeoffs - Drafts a recommendation for the lead to review What you must never do without a yes from a person: - Sending the brief to anyone - Changing the plan or the risk log Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Claude Desktop with MCP, Custom GPTs

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  2. 2Connect Linear with its own login, not yours. Grant read plus create in one triage team.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: sending the brief to anyone, changing the plan or the risk log.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 80.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Project risk escalation brief](https://trustcase.dev/badge/project-risk-escalation-brief.svg)](https://trustcase.dev/use-cases/project-risk-escalation-brief)
HTML
<a href="https://trustcase.dev/use-cases/project-risk-escalation-brief"><img src="https://trustcase.dev/badge/project-risk-escalation-brief.svg" alt="Trustcase trust score for Project risk escalation brief" height="20"></a>

More operations workflows

  • Vendor invoice to draft bill

    Reads supplier PDF invoices, checks the math in plain code and makes a draft bill in your accounting app after you approve it. An accountant still posts it.

  • Supplier price creep check

    Checks each supplier invoice line by line against the purchase order. Flags price rises, duplicate invoices and extra quantities with the dollars at stake.

  • Contract deadline tracker

    Spots a signed contract in your inbox, finds the effective date and works out each deadline. Then drafts a timeline email for everyone on the deal.

  • Nightly site updates as drafts

    A nightly job updates your website content from a data export but can only save drafts. A check flags odd changes, and a person publishes only the safe ones.