Is your repository factory-ready?
Ten yes or no questions about your repository and your tickets. Tick the ones that are true today. The score tells you whether an AI coding agent can safely open pull requests on it, and what to fix if not.
The ten checks
Answer for the repository you would start with. One is enough.
What your score means
0 of 10
Tick the checks above to see your result.
What to fix first
Your unchecked items, in the order we would fix them.
- 01Tests run automatically in CI on every pull requestAdd a CI workflow that runs your test suite on every pull request, even while the suite is small.
- 02Tickets have written acceptance criteriaWrite two or three acceptance criteria on each ticket before it enters the start column.
- 03Branch protection is on for the main branchTurn on branch protection for main and require at least one review before a merge.
Then 7 more, in the same order.
Get the checklist as a PDF
The same ten checks with the why and the fix for each, to share with your team.
Questions about the checklist
What does factory-ready mean?
A factory-ready repository has the gates an AI coding agent needs before it can open pull requests safely: tests that run on every pull request, tickets with written acceptance criteria, a protected main branch, secrets kept out of the code and a named person who approves merges. The ten checks on this page test exactly those gates.
Does a low score mean we cannot use a software factory?
No. It means the first work is on the repository, not on the agent. Most teams start by adding automated tests and writing acceptance criteria into tickets, because without them an agent's pull requests cannot be reviewed with confidence. Fix the unchecked items in the order listed, then re-score.
Which check matters most?
Tests that run automatically in CI on every pull request. They are the signal that tells a reviewer, and the agent itself, whether a change works. Written acceptance criteria come second, because they define what the agent is asked to build. The other eight checks protect the code and make reviews quicker.
Do we need to pass all ten before starting?
Not necessarily. A score of nine or ten means you can start with one repository and one narrow workflow. At seven or eight, fix the remaining items first, which is usually a short job. Below seven, start with tests and written requirements, and we will say the same on a call.
Ready for the next step?
If the score says ready, or close, we set up the loop on one repository and hand it over to your team.