Patterns
A catalog for agentic work
Reusable shapes that keep showing up once you let an agent touch a real repository. Each one says what problem it solves, how it is implemented, what it costs, and when it is the wrong tool. Short by design - they are meant to be linked to, argued with, and copied.
core5
01Plan as artefactThe agent writes the plan to a file in the repository, before writing any code, and the human gate happens there.1 minopen →02Context budgetAllocate the window deliberately across layers - instructions, project facts, working set, history - instead of filling it until it overflows.1 minopen →03Tests the agent cannot authorWrite the acceptance test yourself, run it before the code exists, and never let the agent weaken it to go green.1 minopen →04Separate author and reviewerA second agent with a fresh context reviews the diff against the task, not against the author's reasoning.1 minopen →05Blast radiusConstrain what a run can touch, so that a wrong answer is cheap to roll back rather than expensive to discover.1 minopen →
supporting1