The problem
Most agent projects skip the questions that would have caught failure early.
Teams build agents before they know what they are for.
Nobody says when a person must step in.
Nobody can prove the agent works.
User research, service design, interaction design, content, business analysis, accessibility, and performance.
Each agent drops into your own AI tool, works one stage at a time, and stops for your yes.
Every one is built with the same five-question method — published in full.
Or get all nine in the UCD Team bundle
Works in Claude Code and Cursor · Your own AI keys · Nothing to host · WCAG 2.2 AA built in
The problem
Teams build agents before they know what they are for.
Nobody says when a person must step in.
Nobody can prove the agent works.
Every agent answers five questions before it is built. You can read every answer.
What goes in the zip once the five questions are answered.
| File | Answers | Contents |
|---|---|---|
instructions.md | 1, 2 | Role, voice, tone, refusals, two worked examples |
skills/ | 1 | One file per skill: inputs, steps, outputs, evidence rule, gate |
tools.md | 3 | Every connection with read/write scope and fallback |
manifest.md | 3 | Which skill uses which tool. No gaps, no guesses |
guardrails.md | 2, 4 | Each risk, its control, its owner, sign-off |
memory.md | 2 | What is kept, where, how long, who agreed it |
evals/ | 5 | Test inputs, expected outputs, pass marks, last score |
Each package is built to a named standard. All nine are available on Gumroad.
A whole user-centred design team of AI agents in one purchase. Start with UCDOps Manager to plan who you need, then hand the work to the specialists. Each one drafts. Your people decide.
No hosting. Your keys. Your tool.
Who built the method and the nine agents
AI agent designer
Twenty-two years across engineering, UX, product and service design, including eight on GOV.UK.
I design agents for UK public sector teams before anyone writes a prompt — method first, then the zip.