---
titel: "Blog"
adresse: https://anvil-coder.tech/en/blog
beschreibung: "Articles on the path from a requirements text to a finished repository — insights into process, decisions, and day-to-day practice with Anvil Coder, published as they come."
sprache: en
---

Blog

# Articles from building Anvil Coder

The blog follows how Anvil Coder turns a requirements text into a verified repository — concrete runs, decisions, and what shows up along the way.

## What this blog is

This blog isn't an announcement channel, and it isn't marketing copy on a schedule. It follows individual Anvil Coder runs the way they actually unfold — the decisions a requirements text forces on the way to a finished repository, and what shows up when a result doesn't match the first mental picture of it.

Articles appear irregularly, whenever a run or a change to the system produces something worth writing down in a traceable way. Anyone wanting the mechanics behind the decomposition into TaskSlices or the phase model can find that explained on the page „Wie es funktioniert" (German only for now) — this blog shows the practice, not the theory.

## All articles

- 2026-08-26[One epic, four trackers, one gesture](https://anvil-coder.tech/en/blog/ein-epic-vier-tracker-ein-handgriff)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.

- 2026-08-17[Spec-driven development: the spec is the source, not the chat log](https://anvil-coder.tech/en/blog/spec-driven-development)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.

- 2026-08-10[Why oversight isn't an all-or-nothing choice](https://anvil-coder.tech/en/blog/aufsicht-ist-keine-alles-oder-nichts-frage)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.

- 2026-08-03[Why the commit history is the real proof](https://anvil-coder.tech/en/blog/commit-historie-als-nachweis)"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.

- 2026-07-27[Why architecture rules belong in the prompt, not in a wiki](https://anvil-coder.tech/en/blog/architekturvorgaben-im-prompt)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.

- 2026-07-20[Why a TaskSlice has to be small](https://anvil-coder.tech/en/blog/warum-taskslices-klein-sind)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.

- 2026-07-13[Getting started with Anvil Coder](https://anvil-coder.tech/en/blog/erste-schritte)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.

## Want the mechanics behind it?

How the decomposition into TaskSlices works is explained in full on the page „Wie es funktioniert

[Kostenlos starten](https://app.anvil-coder.tech/register)[Demo vereinbaren](https://anvil-coder.tech/demo)