Ten files changed, pull request open, four minutes of work. The agent ships – but nobody reads what's being produced anymore. What happens to the domain logic when code stops being the artifact humans use to verify it? And why do teams get slower even as they produce code faster?

As a Microsoft MVP for Developer Tools, Daniel helps teams build agent-driven workflows – and shows the patterns where they consistently break down: architectures that erode under the flood of files, untested legacy code, requirements that end up in the prompt instead of in acceptance criteria. His antidote isn't a better prompt – it's determinism: acceptance criteria as executable BDD scenarios, TDD as a stopping condition, hooks that actually enforce the rules. Because "please test the code at the end" in your AGENTS.md isn't a quality gate – it's a request.