← All writing

Defining finished for an AI agent

Building a catch-up workflow that can resume unfinished work without turning every session into another inventory.

I wanted a simple way to open a repository and have an agent continue the work already waiting there. The TODO list and handoff notes should have been enough to get started. In practice, I kept having to explain that I wanted the unfinished work completed, and that finding the list was only the beginning.

That became the brief for a /catchup skill. It would read the existing project records, identify work it could carry out, and bring me any decisions that genuinely needed my input before starting. After those decisions, it should keep going until the agreed work was done.

The distinction matters when I’m working on personal projects around other commitments. If I have to reconstruct the state of every repository before an agent can help, the handoff documents aren’t doing much for me. I want to spend that time deciding what the project needs or reviewing something concrete.

What the skill needed to know

A useful catch-up process has to understand more than a task list. Some items may already be finished on another branch. Others may depend on a decision recorded elsewhere. A note saying something needs the owner can also be out of date if the answer is already in the repository.

The initial skill captured the behavior I wanted: collect the open work, ask the necessary questions up front, then continue. It also needed a clear stopping point. An agent shouldn’t expand a maintenance request into unrelated work just because it can find more things to change.

The first version was written and made available to my agent setups. I planned to try it in a fresh thread. At that point, installation was the result I could confirm from the session report; the behavior still needed a real run.

I’m treating these small workflows as things I can revise through use. The prompt needs to make the intended outcome clear, but the next session is where I find out whether it actually reduces the amount of coordination I have to do. For this one, the test was straightforward: could I start from the existing records and get completed work back, with only the decisions that required me left open?

Written by . Follow via RSS ↗