Skip to content

Daily product spec risk triage against compliance rules

Each morning a second line risk reviewer reads product requirement docs completed in the last day from the team wiki and grades six risk areas against the company's ICT and regulatory framework. It outputs one report per document and changes nothing.

OperationsWorks with Claude Desktop with MCP · Custom GPTs+1Community example

What it does

  • Fetches requirement docs updated or completed in the last 24 hours
  • Classifies each as clean, needs pushback or high risk
  • Scores availability, privacy, integrity, regulatory, third party and complexity risk with a short rationale
  • Lists remedial steps for the document owner
  • Produces one audit report per document in a fixed schema

Your approval boundaries

Read only

Reads connected data. It does not send messages or change records.

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 fetches requirement docs updated or completed in the last 24 hours. Next, it classifies each as clean, needs pushback or high risk. Then it scores availability, privacy, integrity, regulatory, third party and complexity risk with a short rationale. After that, it lists remedial steps for the document owner. Finally, it produces one audit report per document in a fixed schema. It works with your knowledge base and docs, each on its own login with limited access.

You get the finished work, ready to read. It only reads, so nothing is sent, changed or paid for. You decide what to do with it.

“Paste this trigger prompt into the project chat interface every morning”
Nichita Bradu nichitabradu-tr on GitHub · Oct 21, 2026
Before you startKnowledge base · Docs accessRead-only permissionsClaude Desktop with MCP or Custom GPTs
Explore required tools and model recommendations

Tools and access

  • Notion

    Handles the knowledge base part of this job. Grant only the pages it needs, read first.

    API required: Yes. Needs a Notion integration. You choose which pages it can see by sharing them with it.

  • 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.

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. last 24 hours

2Your prompt

4 of 4 still empty
Fill these in before you run it: [REQUIREMENTS REPOSITORY PAGE] [RISK FRAMEWORK DOCUMENTS] [LOOKBACK WINDOW: e.g. last 24 hours] [WHO RECEIVES HIGH RISK FLAGS] You are the Daily product spec risk triage against compliance rules agent. Each morning a second line risk reviewer reads product requirement docs completed in the last day from the team wiki and grades six risk areas against the company's ICT and regulatory framework. It outputs one report per document and changes nothing. 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: - Fetches requirement docs updated or completed in the last 24 hours - Classifies each as clean, needs pushback or high risk - Scores availability, privacy, integrity, regulatory, third party and complexity risk with a short rationale - Lists remedial steps for the document owner - Produces one audit report per document in a fixed schema What you must never do without a yes from a person: - Anything that writes, sends, or spends. This job only reads. 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 Desktop with MCP, Custom GPTs, Claude Code

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 Notion with its own login, not yours. Grant only the pages it needs, read first.
  2. 2Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  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.

Access30 / 30

Read only. It never writes, sends or spends.

Human approval30 / 30

Nothing to approve, it only reads.

Undo and logs20 / 20

No changes to undo. Reads can be logged.

Scope18 / 20

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

How to raise it

Nothing major to fix. One polish tip: show a short daily log of what it read, so you can spot it reaching for anything new.

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 Daily product spec risk triage against compliance rules](https://trustcase.dev/badge/daily-product-spec-risk-triage-against-compliance-rules.svg)](https://trustcase.dev/use-cases/daily-product-spec-risk-triage-against-compliance-rules)
HTML
<a href="https://trustcase.dev/use-cases/daily-product-spec-risk-triage-against-compliance-rules"><img src="https://trustcase.dev/badge/daily-product-spec-risk-triage-against-compliance-rules.svg" alt="Trustcase trust score for Daily product spec risk triage against compliance rules" height="20"></a>

Other workflows that use the same tools

  • Low effort weekly meal plan

    Personal. Plans a few meals a week that make leftovers, take little prep and share ingredients. Cuts food waste and the nightly dinner question.

  • Personal wiki upkeep with recommend and lint passes

    Personal. Three scheduled tasks keep a personal markdown wiki honest. A daily pass archives chat sessions as raw notes, a weekly pass recommends what is durable enough to promote, and a monthly lint flags contradictions, stale claims and broken links.

  • Lead research brief

    Sales. Turns a new inbound lead into a one page brief before your first call.