Friday business review from the week's history and notes
On Fridays it reads the week's commit history, your notes and last week's review before asking anything. Then it writes what shipped, what is stuck with a next move and an owner, the decisions made and the one thing to automate next.
What it does
- Reads the week's commit history, notes and last week's review
- Lists what shipped and what is stuck, each with a next move and an owner
- Records decisions made into a decisions folder
- Picks the one thing to automate next
- Saves the review to a reviews folder
Your approval boundaries
Creates draftsThese actions always wait for your yes:
- Sharing the review outside your notes
- Building any automation it picks
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 week's commit history, notes and last week's review. Next, it lists what shipped and what is stuck, each with a next move and an owner. Then it records decisions made into a decisions folder. After that, it picks the one thing to automate next. Finally, it saves the review to a reviews folder. It works with your git host and notes app, 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 sharing the review outside your notes and building any automation it picks, and says plainly if a step cannot be undone.
“a Friday review keeps the week honest”
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.
Notion
Handles the notes app 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.
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.
2Your prompt
4 of 4 still emptyYour 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.
- 1Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
- 2Connect Notion with its own login, not yours. Grant only the pages it needs, read first.
- 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
- 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.
- 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.
Writes drafts and notes inside your tools, nothing leaves on its own.
Waits for a yes on: sharing the review outside your notes, building any automation it picks.
Leaves drafts you can throw away, with a record of what it made.
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.
[](https://trustcase.dev/use-cases/friday-business-review-from-the-weeks-history-and-notes)<a href="https://trustcase.dev/use-cases/friday-business-review-from-the-weeks-history-and-notes"><img src="https://trustcase.dev/badge/friday-business-review-from-the-weeks-history-and-notes.svg" alt="Trustcase trust score for Friday business review from the week's history and notes" height="20"></a>More operations workflows
- Weekly purchasing review with late delivery chasers
Once a week it works through purchase orders in a database you own: approvals waiting with their delivery deadlines, items late after partial receipts, invoice prices that differ from the order, and suppliers overdue a review. It drafts supplier chasers and leaves approvals and payments to you.
- New hire access plan from a role matrix with two approvals
When a hire webhook arrives, code builds a least privilege access plan from a role matrix and the model only fills in words. People Ops approves the plan, and IT must also approve any admin or production access. Accounts are created without duplicates and rehires are reactivated rather than recreated.
- Duplicate vendor payment check with a payment hold on approval
Answers back office questions like whether a vendor was paid twice. A code based tool finds the duplicates, high dollar exposure pauses the run for a person, and only an approved result places a payment hold. Every step lands in an audit trail.
- Farm advisory drafts with cited sources and officer sign off
For an agricultural extension office, it reads the week's rainfall forecast, pest alerts and market prices against each household's crop stage and drafts a plain advisory. Every recommendation cites its bulletin, and the officer signs off before anything goes to a farmer.
Other workflows that use the same tools
- Evidence first support replies
Support. Works the support queue a couple of times a day, checking bug reports against the code before drafting a reply. The owner reviews every reply before it goes out.
- Morning ticket dashboard with tick to approve queue
Engineering. Every morning an agent refreshes a one screen dashboard in your notes from the issue tracker, your workstream notes and inbox. It reads only, proposes board changes as checkboxes and drafts first pass PR reviews that are never posted.
- Printed morning newspaper from your notes
Personal. Every night a routine picks the next unprinted note from a folder and writes it up as a two page newspaper issue. A build step lays it out and checks every page, and a small board on your Wi-Fi prints it at the time you chose.