Imported from Work-In-Progress-For-Health/ai (
projects/manual-testing-to-automatic-testing/AGENTS.md). Install upstream withnpx skills add Work-In-Progress-For-Health/ai --skill manual-testing-to-automatic-testing. Copyright stays with the author.
AGENTS.md
Instructions for AI coding agents working in this repository (any tool — Claude Code, Codex, Copilot, Cursor, etc.). If you are specifically Claude Code, also read CLAUDE.md.
What this repository is
A single, comprehensive guide for NHS Wales / Digital Health and Care Wales (DHCW) manual software testers whose teams are moving towards test automation. It is documentation, not software: no build step, no tests to run, no dependencies to install.
The two hard rules
spec/*.mdis the single source of truth. Facts used inREADME.md— NHS Wales Organisational Change Policy (OCP) provisions, the PADR process, DHCW's Welsh Government oversight status — are specified inspec/first. IfREADME.mdandspec/disagree,spec/is correct; fixREADME.mdto match it.README.mdcontains the entire guide and must not be split into multiple files. This was tried (aguide/directory with one file per part) and explicitly reversed by the user, who required the whole guide — every section, every checklist — to be readable in the singleREADME.mdfile.README.mdis exempt from the 40KB file-size guideline below; every other file in this repo should stay under it.
File layout
| Path | Purpose | Size target |
|---|---|---|
README.md |
The entire guide: all numbered sections and checklists | No limit (explicit exception) |
index.md |
A short pointer to README.md and spec/ |
A few KB |
spec/index.md |
OCP policy facts: source of truth | Under 40KB |
spec/padr.md |
PADR process facts: source of truth | Under 40KB |
CLAUDE.md |
Claude Code-specific instructions | Under 40KB |
AGENTS.md |
This file | Under 40KB |
AGENTS/style.md |
Tone, language, and formatting rules | Under 40KB |
AGENTS/structure.md |
Section numbering, anchors, checklist conventions | Under 40KB |
AGENTS/sources.md |
How to verify and cite factual claims | Under 40KB |
Read AGENTS/style.md, AGENTS/structure.md, and AGENTS/sources.md before making a non-trivial content edit — each covers one concern in more depth than fits here.
Workflow for a content change
- Fact change (policy, process, DHCW status)? Update the relevant
spec/*.mdfile first. - Update
README.mdto match. Search (grep -n) for every place the changed fact, term, or cross-reference appears — key facts repeat across many sections by design, and a partial edit leaves the guide self-contradictory. - Changed a heading's text? Its anchor slug changes too. Find and fix every internal
[text](#n-old-slug)link that pointed at it, including the numbered Contents list. - Re-check file sizes:
README.mdis expected to be large; everything else should stay under 40KB.
Quick-reference constraints (see AGENTS/style.md for full detail)
- No bold Markdown (
**text**). No emoji. - "Automatic testing" for the practice/discipline; "automated test(s)" is fine for the artifacts.
- Playwright and Selenium mentioned together always also list WebDriver.
- Support contacts are POD/HR and the trade union rep — never "your manager."
- Prefer affirmative phrasing over "no X, no Y" listing constructions.
- Most sections and subsections end with a
Checklist: ...block of- [ ]first-person items.
Don't
- Split
README.mdinto multiple files. - Add facts to
README.mdwith no corresponding entry inspec/. - Reintroduce bold markup, emoji, or "your manager" as a contact.