What problem does it solve? Jumping straight into code on non-trivial work locks in the wrong structure early. This Skill forces design-first thinking: it grounds the problem in the existing system, generates multiple competing architecture sketches in parallel, synthesizes the best one, and only then fills in implementation against the agreed contract. ## Core Features & Use Cases - Grounded design exploration: Traces the existing system (via the anvil-how skill, git history, and ADRs) so new designs respect real constraints instead of guesses. - Parallel candidate sketches: Runs multiple model runners through anvil-arena, each producing a type sketch, signatures, module map, and prose rationale, then synthesizes one design. - Red-flag screening and scrap loop: Rejects shallow modules, information leakage, temporal decomposition, and pass-through methods, and triggers a full redesign when implementation friction reveals a wrong architecture. - Use Case: Before building a new billing module, invoke the architect to produce two structurally distinct designs, compare their interface depth, ship the chosen skeleton as a scaffold commit, and implement against it. ## Quick Start Ask the assistant to architect the new feature before writing any code, describing the problem and the systems it must integrate with.
