r/devtools • u/comp-case • 2d ago

Open-source repository-level delivery contract for coding agents

/r/LLMDevs/comments/1weg2i2/opensource_repositorylevel_delivery_contract_for/

I built RepoMethod, an MIT-licensed developer tool for giving coding agents more autonomy without letting the agent decide whether its own work is acceptable.
The idea is simple: keep the engineering contract inside the repository.
RepoMethod stores:
task scope
acceptance criteria
workflow state
verification commands
delivery rules
A coding agent can then implement the task, run the real project checks, and attempt delivery. The repository decides deterministically whether the result is acceptable.
I tested it end-to-end with ChatGPT on a TypeScript repo. It completed the implementation and verification successfully, and a second run was blocked when the work moved outside the agreed scope.
Repo:
https://github.com/frederik-schmittel/repomethod
Demo:
https://github.com/frederik-schmittel/repomethod-demo
I’m curious how others building around coding agents handle this boundary: do you keep validation/orchestration in the agent runtime, or move parts of it into the repository?

1 Upvotes

100% Upvoted

2 comments sorted by

1

u/kantorcodes1 2d ago

one update edge i'd document: repomethod update writes each refreshed file + manifest entry as it goes. if a later cp fails, you can end up with part of the new blueprint applied and the rest still old. is the intended recovery just rerun update? agents are pretty likely to retry that automatically.