Add a new region's program rules to existing software with staff sign-off
A coding assistant takes the existing codebase and a region's rules, writes a tested implementation, and local program staff verify each rule before release.
The use case
Mid-Ohio Food Collective describes how its FreshTrak software, used by food banks, is extended to new states. Engineers give Claude Code the full codebase plus a new state's regulations, and it produces a tested implementation. Then the engineering team and local program staff read each requirement, compare every rule with the state's own guidance, and approve it before release. Changes also need a human engineer's sign-off, passing automated tests and an assisted code review pass. The pattern suits any software where rules differ by region and a wrong rule affects real people. Keep a program expert as the final reviewer.
Example workflow
- Gather the new region's written rules and guidance into a single folder.
- Ask the coding assistant to propose changes against the existing codebase, with tests for each rule.
- Program staff read each rule in plain language and compare it to official guidance.
- Engineers review the pull request, run the automated tests and do an assisted review.
- A person approves the merge and release; staff spot-check live behaviour after launch.
Tools
- Claude Code
- Claude Tag
- Git pull requests
- Automated tests
Risks and guardrails
- A misread regulation can deny people benefits; require a named program expert to sign off on each rule.
- Tests that mirror the assistant's own reading can miss the same mistake; write some from the official examples.
- Old codebases have hidden dependencies; review changes in small pull requests.
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Mid-Ohio Food Collective, Anthropic customer story: claude.com/customers/mid-ohio-food-collective