Loops

Loops: recurring engineering work, handed to an agent.

Trigger
Goal
Artifact
Handoff

Anatomy

How a loop works

01

Trigger

02

Goal

03

Artifact

04

Handoff

The whole point: loops do the legwork. The judgment stays with you.

The loops

The loops

Loop

01

Dependency triage loop

If you have Dependabot or Renovate on, you know the pile. A stack of updates lands and they are not equally important: some are boring patch bumps, some are security fixes, some look small until you realize they touch a risky part of the stack.

This loop works the pile so you don't merge blind: it clears the safe bumps, fixes what's broken, and ranks the rest by risk.

Trigger
Goal
Artifact
Handoff

It merges the boring, safe bumps and pushes obvious CI fixes. The risky ones it leaves untouched with a written assessment: major bumps, breaking changes, anything uncertain. Your attention goes to the calls that actually need a human.

Loop

02

Release review loop

You merge a PR. Did it actually ship? Most teams can't answer that without digging through releases and compare views by hand. And the open PRs you're waiting on: are their deploy gates finally clear, or still blocked on something upstream?

This loop answers both, read-only: what shipped, whether your merged work made it into a release, and which open-PR gates have cleared.

Trigger
Goal
Artifact
Handoff

It takes no write actions: no merges, no label changes, no messages. Every suggestion comes back as a question you approve later. A review surface, not an actor.

Loop

03

Documentation drift loop

The problem with docs isn't that nobody knows they matter. It's that implementation moves, releases ship, setup steps change, and the docs quietly fall behind because nobody is explicitly watching for it.

This loop watches for it: it reads your code and your docs, finds where they've diverged, fixes the clear low-risk drift itself, and flags the rest.

Trigger
Goal
Artifact
Handoff

It only auto-fixes drift that's clear and low risk: docs-only, verified, conventional commit. Anything ambiguous it leaves alone and reports, with the exact source and stale docs, for you to decide.

Loop

04

Weekly meeting prep loop

I have a recurring team meeting, and before it I want to reconstruct what actually changed since the last one. Not status theater. Not a fake AI standup. Just a clean prep artifact so when it's my turn I can talk clearly about what moved.

Trigger
Goal
Sources
Artifact
Handoff

These tools are good at reconstructing a scattered week. They are not good at deciding what matters politically, or how to talk about it in the room. That part stays yours.

In progress

05

RFC drift loop

The one I'm building

Teams write an RFC, everyone agrees on the plan, then implementation starts moving. Edge cases show up. The rollout changes. A decision gets made in a PR thread. A month later the project is still moving, but the RFC is no longer a clean record of what's actually happening.

This is the one I haven't run yet. It's where I think the pattern goes next. The job isn't to rewrite the RFC behind your back. It's to compare the plan against execution and prepare a drift report.

Trigger
Goal
Artifact
Handoff

This one pushes the pattern further. We're no longer summarizing a surface. We're comparing a system's stated intent against what actually happened.

The pattern

The pattern

Not prompts. Not generic background agents. Not "AI engineer, go run the team."

The useful pattern is loops: a clear trigger, a clear goal, a reviewable artifact, and a clean handoff at the judgment boundary.

It gets more interesting once you stop asking "what prompt should I write?" and start asking "what recurring engineering loop should exist here?"

Repos

Related repos