Steal our workflow

A settings design passed its technical checks and still came back for another pass. I liked the new navigation. The actual settings inside it needed more work.

That is the kind of distinction an agent needs written down. Passing the checks and liking the result answer different questions. Our workflow gives them different steps, with evidence attached to each.

We’ve published that workflow as a pack of skills. They’re Markdown files an agent reads before it works. You can read them before installing anything.

Start before the code

Capture writes down the request. Refine settles what it means and how we’ll know it worked. Prep reads the affected code and records a plan. Go implements it and gets an independent review. Ship handles release under a grant for one issue.

There is also a base skill for using Hydrant and a review-triage skill for working through pull-request feedback. The pack keeps the task in the tracker, where scope and status survive the end of a chat.

The distinction between prep and go is useful. An agent can tell me what it found and how it would verify the change before it edits anything. Sometimes that is enough to discover that the issue asks for the wrong thing.

Your repository keeps its own rules

The setup skill reads the repository first. It looks at the workflow already there, the checks it can run and the way releases happen. Then it proposes an installation plan.

An existing skill with the same name stays yours. The repository’s base branch, verification commands and definition of finished work belong in its own profile. Copying our process shouldn’t quietly copy our deployment assumptions.

Ship is deliberately explicit. The public pack asks for a grant in the current conversation for the issue being released. An old comment saying someone gave permission doesn’t do the job.

Take the useful parts

The pack is MIT-licensed. Change it. Keep a step, remove a step, or read it and decide your current process is better.

Our own procedures have changed as we’ve watched agents use them. A sentence that seemed clear to us sometimes left two plausible interpretations. The next revision had to say which one we meant.

The install guide covers setup. Bring a real issue and your repository’s actual check commands. You’ll learn more from the first handoff than from polishing the instructions in the abstract.