Skip to content

As built docs updated from change evidence

Takes a diff, deploy result or test result and drafts matching updates to your architecture doc, config guide and change log. It never claims more than the evidence proves, and writes only the edits you approve.

EngineeringWorks with Claude Code · CursorCommunity example
Build your promptSee requirements

What it does

  • Redacts secrets from the evidence before reading it
  • Picks which docs, sections and rows the change affects
  • Caps each status at what the evidence can prove
  • Shows the diff and any open questions
  • Refuses to write if a doc changed since the proposal

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Writing any edit to the docs
  • Marking anything as verified on a person's word

You decide what happens next.

More about this workflow

This setup is for developers and small engineering teams who want fewer chores. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it redacts secrets from the evidence before reading it. Next, it picks which docs, sections and rows the change affects. Then it caps each status at what the evidence can prove. After that, it shows the diff and any open questions. Finally, it refuses to write if a doc changed since the proposal. It works with your git host and docs, 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 writing any edit to the docs and marking anything as verified on a person's word, and says plainly if a step cannot be undone.

“writes only the edits you approve.”
VAROIndustries VAROIndustries on GitHub · Oct 18, 2026
Before you startGit host · Docs accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

    Sign up: Create a GitHub account

  • 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

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Opus 5.5

Its maker points to it for long running coding work.

$4 per million input tokens, $20 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

Claude Sonnet 5.5

Half the price per token and still strong for reviews and docs.

$2 per million input tokens, $10 per million output tokens.

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

diff, deploy log or test result

2Your prompt

3 of 3 still empty
Fill these in before you run it: [DOCS FOLDER] [EVIDENCE: diff, deploy log or test result] [ENVIRONMENT NAME] You are the As built docs updated from change evidence agent. Takes a diff, deploy result or test result and drafts matching updates to your architecture doc, config guide and change log. It never claims more than the evidence proves, and writes only the edits you approve. 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: - Redacts secrets from the evidence before reading it - Picks which docs, sections and rows the change affects - Caps each status at what the evidence can prove - Shows the diff and any open questions - Refuses to write if a doc changed since the proposal What you must never do without a yes from a person: - Writing any edit to the docs - Marking anything as verified on a person's word 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, Cursor

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 GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  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.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval30 / 30

Waits for a yes on: writing any edit to the docs, marking anything as verified on a person's word.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope18 / 20

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

How to raise it

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

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 As built docs updated from change evidence](https://trustcase.dev/badge/as-built-docs-updated-from-change-evidence.svg)](https://trustcase.dev/use-cases/as-built-docs-updated-from-change-evidence)
HTML
<a href="https://trustcase.dev/use-cases/as-built-docs-updated-from-change-evidence"><img src="https://trustcase.dev/badge/as-built-docs-updated-from-change-evidence.svg" alt="Trustcase trust score for As built docs updated from change evidence" height="20"></a>

More engineering workflows

Other workflows that use the same tools

  • Morning signal sweep with sales handoff budget

    Sales. Each morning it reads every new account signal against your written ICP, stage rules and plays, and proposes which ones become a sales handoff, with the evidence cited. Sales never gets more handoffs than the weekly budget, and nothing is sent or written to the CRM.

  • Proposal first draft

    Sales. Builds a proposal from your template and the discovery notes.

  • Weekly ops report

    Operations. Writes the Monday numbers summary so you do not build it by hand.