Jürgen Helmers joins Beyond Vibe Coding to explain how Andercore is moving from individual AI usage toward loop and harness engineering across a distributed engineering organization. The conversation gets very concrete: Claude-based workflows, markdown skills, Jira and wiki connectors, engineering vision files, review agents, issue files, blocker/major gates, circuit breakers, milestone loops, red/green agents, automated documentation and model routing across planning, implementation, review and third-party integrations. The interesting point is not the tool list; it is the system around the tools.

The strongest thesis of the episode is that agentic engineering moves the bottleneck left. Once Jürgen’s team had loops that could produce and review useful software, the limiting factor became PRD quality, stakeholder clarity and architecture context. Andercore responded with agent-led grilling sessions that poke holes into plans, generate open questions and translate technical issues into the language of logistics, sales or procurement. Faster engineering did not remove planning work. It made weak planning visible much sooner.

The episode also avoids the simple productivity story. Jürgen describes the human cost of running several loops in parallel, the difficulty of keeping a distributed organization in sync when senior engineers adopt the harness quickly, and the unresolved career question of how junior engineers learn when agents abstract away many old failure paths. For CTOs, engineering managers and CPOs, this is a practical conversation about operating model design, not a tooling demo.

–

Links and References

Andercore: https://andercore.com/about-usDr. Jürgen Helmers on LinkedIn: https://de.linkedin.com/in/dr-j%C3%BCrgen-helmers-94b8969