Ticket to PR · A path without reconstruction
Six agent PRs of 800 lines each in the queue, no trace of why. Stand-up in an hour. Anvil Coder delivers the opposite: a ticket becomes a chain of small, named commits, each with the task it came from, handed over as a draft pull request in your repository. The reviewer reads instead of guessing.
In the internal board or in Jira, YouTrack, GitHub or GitLab: dragging a story to “Ready” is enough. There is no other start button.
The task is broken into small work steps with dependencies. Open points stand as assumptions in the run, not hidden in the code.
Every work step runs under the same guardrails, is built and tested and leaves its commit. What fails is repaired before the run moves on.
The draft PR sits at your code host. Diff, acceptance criteria and check report stand side by side. You merge if it fits.
Example
The customer has been asking for two weeks, the team has no room. The title alone leaves a lot open; four sentences of acceptance criteria turn it into a task a machine can carry out and a person can judge:
The next morning the draft PR is there: endpoint, service, tests, docs, four commits. The check report shows what ran. Your review takes as long as a coffee.
Enough context for someone who does not know your project: the affected feature, the intended behaviour, what must explicitly not change. Small and clearly bounded beats ambitious for a first task.
For a larger undertaking you start in Spec Studio: the specification becomes epics and stories that you curate before any of them runs.
Three things side by side: what was asked, what changed, what was checked. The commit history tells the implementation step by step; the run report records the checks that ran.
A check covers what it checks. Whether the solution is the right one for the domain stays your call, and that is exactly what you now have time for again.