Plan
Requirements are structured, open points are made visible as assumptions and turned into a directed work graph.
The principle
The Anvil Coder software factory treats an order as a production plan: requirements are broken down into small work steps, executed by specialised workers and checked at every station against the same guardrails. What stands at the end is not a suggestion but a traceable Git repository.
A large project does not fit into a single prompt. The factory solves this problem not with a bigger wall of text but by cutting to size: every task becomes a small, comprehensible slice with exactly the context it needs.
The coordinator holds the overall plan. Workers build the individual parts, test them and leave their commits behind. Phase barriers pin down the order where it matters for the domain; within a phase there is room for parallel work.
Requirements are structured, open points are made visible as assumptions and turned into a directed work graph.
Every slice gets its own worktree. The model works with a bounded context instead of failing against one unmanageable overall prompt.
Guardrails, builds, tests and consistency gates check the result. A failure becomes a capped repair round, not a silent exception.
Every station leaves traces: commits, checks and an audit trail make visible how the repository emerged from the requirement. People keep the authority to decide; the repeatable machine work covers the distance in between.