# From prompt to loop to graph engineering

[Skip to content](#lm-inhoud)Network/[NL](/en/van-prompt-naar-graph-engineering)EN[Hubhub.llmnet.nlCompare models on task, language, cost and license.](https://hub.llmnet.nl/en/)[Communitycommunity.llmnet.nlPrompt techniques, patterns and system prompts.](https://community.llmnet.nl/en/)[APIapi.llmnet.nlLLMs in production: rate limits, routing, structured output.](https://api.llmnet.nl/en/)[Consultancyconsultancy.llmnet.nlRolling out AI in an organization, pilot to production.](https://consultancy.llmnet.nl/en/)[Newsnieuws.llmnet.nlAI developments, explained for the Netherlands.](https://nieuws.llmnet.nl/en/)[Benchmarkbenchmark.llmnet.nlMeasure AI quality yourself, on your own tasks.](https://benchmark.llmnet.nl/en/)[Careersvacatures.llmnet.nlAI roles, salaries and career paths in the Netherlands.](https://vacatures.llmnet.nl/en/)[Learnleren.llmnet.nlAI concepts in plain language, beginner to builder.](https://leren.llmnet.nl/en/)[Guidegids.llmnet.nlRun AI privately on your own Mac, PC, NAS or home server.](https://gids.llmnet.nl/en/)[Directorydirectory.llmnet.nlMapping the AI ecosystem: tools, models, companies.](https://directory.llmnet.nl/en/)[Radarradar.llmnet.nlSignals from X, research and communities for indie developers.](https://radar.llmnet.nl/en/)[Appsapps.llmnet.nlReviews of AI apps and open-source repos, with tips for builders.](https://apps.llmnet.nl/en/)[llmnet.nl — main site](https://llmnet.nl/en/)[](https://x.com/intent/post?url=https%3A%2F%2Fcommunity.llmnet.nl%2Fen%2Fvan-prompt-naar-graph-engineering&text=From%20prompt%20to%20loop%20to%20graph%20engineering)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcommunity.llmnet.nl%2Fen%2Fvan-prompt-naar-graph-engineering)[](https://www.reddit.com/submit?url=https%3A%2F%2Fcommunity.llmnet.nl%2Fen%2Fvan-prompt-naar-graph-engineering&title=From%20prompt%20to%20loop%20to%20graph%20engineering)[](#)[](https://x.com/intent/post?url=https%3A%2F%2Fcommunity.llmnet.nl%2Fen%2Fvan-prompt-naar-graph-engineering&text=From%20prompt%20to%20loop%20to%20graph%20engineering)[](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcommunity.llmnet.nl%2Fen%2Fvan-prompt-naar-graph-engineering)[](https://www.reddit.com/submit?url=https%3A%2F%2Fcommunity.llmnet.nl%2Fen%2Fvan-prompt-naar-graph-engineering&title=From%20prompt%20to%20loop%20to%20graph%20engineering)[](#)By Ivo Donker — created with AI assistance (Claude & Gemini) · Last updated: July 31, 2026

[← LLMnet Community](/)

# From prompt to loop to graph engineering: what changes at each layer

## Three layers, not competitors

Prompt, loop and graph engineering are stacked “units of control”, not competing methods. A prompt steers one response; a loop steers one agent's repetition cycle (goal, tools, repetition, stop condition); a graph steers the organisation of multiple agents through nodes and edges. Each layer keeps the layers beneath it intact.

The terminology is young: loop engineering broke through in June 2026, graph engineering as a term in July 2026 — helped by tooling such as LangGraph (StateGraph, conditional edges) and the agent features in Claude Code and Codex.

## What makes a loop good

Six elements recur in descriptions of loop engineering: scheduled automations, worktrees for parallel isolation, reusable skills, plugins/connectors (often via MCP), sub-agents with a maker/checker split, and persistent state outside the conversation.

The main pitfall is measurability: a loop that cannot mechanically distinguish “done” from “stuck” does not fail loudly — it keeps spending tokens. Verifiable success criteria (tests, schemas, rubrics, or a second model as judge) are a precondition, not a luxury.

## What a graph adds

Graph engineering describes multi-agent systems as a topology: node functions receive state and return partial updates; context does not cross a node boundary unless an edge carries it explicitly. Production systems distinguish a stable “org graph” (fixed roles) from an ephemeral “work graph” (the current task, with splitting, merging and cancelling).

Caveat: for most solo projects a graph is overkill. The common selection framework is a series of questions — does human review precede every action? can completion be verified non-manually? does the task fit one agent's context? must independent branches run simultaneously? — where the first “no” tells you which layer you need.

## For the indie developer

Practically: start with a good prompt, move to a loop only once you have verifiable success criteria, and to a graph only when independent subtasks genuinely must run in parallel. For the rules of reliable AI coding that precede the loop layer, also read [our explainer of Karpathy's four rules](https://leren.llmnet.nl/en/karpathy-regels-claude-md); daily agent-tooling signals are on [AI Radar](https://radar.llmnet.nl/en/).

Sources: [MarkTechPost, July 29, 2026](https://www.marktechpost.com/2026/07/29/prompt-engineering-vs-loop-engineering-vs-graph-engineering-what-changes-at-each-layer/); background: LangGraph documentation and the agent features of Claude Code/Codex. Verified July 31, 2026.

© 2026 LLMnet Community. Made for developers and prompt engineers.