https://anvil-coder.tech/en/blog Articles on the path from a requirements text to a finished repository. en https://anvil-coder.tech/en/blog/ein-epic-vier-tracker-ein-handgriff https://anvil-coder.tech/en/blog/ein-epic-vier-tracker-ein-handgriff Wed, 26 Aug 2026 00:00:00 GMT Pull an epic onto the trigger state — that is all it takes for Anvil Coder to decompose it into user stories. The gesture is the same on YouTrack, Jira Cloud, GitHub Issues and GitLab Issues; what happens behind it differs per tracker only in transport. And why, deliberately, not a single run starts. https://anvil-coder.tech/en/blog/spec-driven-development https://anvil-coder.tech/en/blog/spec-driven-development Mon, 17 Aug 2026 00:00:00 GMT Spec-driven development answers the drift problem of AI-generated code with a simple inversion: not the prompt history, but a checked specification is the source of truth, and architecture and code only follow from it. That exact ordering is already built into Anvil Coder's phase model. https://anvil-coder.tech/en/blog/aufsicht-ist-keine-alles-oder-nichts-frage https://anvil-coder.tech/en/blog/aufsicht-ist-keine-alles-oder-nichts-frage Mon, 10 Aug 2026 00:00:00 GMT A backlog that grows faster than it shrinks can't just be solved by hiring more people — every new hire raises coordination overhead before it adds throughput. Anvil Coder's approval levels shift the execution instead, not the decision. https://anvil-coder.tech/en/blog/commit-historie-als-nachweis https://anvil-coder.tech/en/blog/commit-historie-als-nachweis Mon, 03 Aug 2026 00:00:00 GMT "We work to OWASP" is a statement of intent. A Git repository where every work step leaves its own commit is a statement of fact — and that difference is what actually holds up when a client asks for proof. https://anvil-coder.tech/en/blog/architekturvorgaben-im-prompt https://anvil-coder.tech/en/blog/architekturvorgaben-im-prompt Mon, 27 Jul 2026 00:00:00 GMT An architecture document that gets read once during onboarding and forgotten after doesn't stop a deviation — it only surfaces in review, once the code already exists. How guardrails turn a team's own rules into a condition of every single step instead, and where that condition stops. https://anvil-coder.tech/en/blog/warum-taskslices-klein-sind https://anvil-coder.tech/en/blog/warum-taskslices-klein-sind Mon, 20 Jul 2026 00:00:00 GMT A TaskSlice isn't just an arbitrarily small chunk of work — it has to fit entirely into a single prompt, together with the context that exact step needs. What that means for decomposition. https://anvil-coder.tech/en/blog/erste-schritte https://anvil-coder.tech/en/blog/erste-schritte Mon, 13 Jul 2026 00:00:00 GMT A first walkthrough of how a requirements text becomes a verified Git repository in Anvil Coder — from the first prompt to the last consistency pass.