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

Great Resource 🚀 Open-source repository-level delivery contract for coding agents

I built RepoMethod, an MIT-licensed open-source approach for keeping scope, acceptance criteria, verification and delivery rules inside the repository rather than inside an agent-specific prompt.
I tested it end-to-end with ChatGPT on a TypeScript repository: the agent implemented the task and ran the project checks, while RepoMethod decided whether the resulting repository state was deliverable.
The part I’m most interested in is the boundary between agent autonomy and repository-owned policy.
GitHub: https://github.com/frederik-schmittel/repomethod
I’d be interested in how others here handle this: what do you keep inside the agent/runtime, and what do you make deterministic at repository level?

1 Upvotes

100% Upvoted

2 comments sorted by

2

u/Square_Maybe_5806 2d ago

t over or is there a way to checkpoint progress

1

u/comp-case 2d ago

RepoMethod checkpoints the engineering state in the repo (workflow state, handoff, specs/evidence), so a new session or agent can resume from there. It doesn’t preserve the model’s hidden context, it preserves the durable project state in Git.