Something new showed up in the prompt engineering corner of Reddit yesterday, and it is not just another workflow builder pretending to be revolutionary. This one lets you sketch your instructions as a graph instead of fighting with a wall of text. This Redditor, who goes by u/Weak_Ad4875, built it after falling down a rabbit hole researching “graph engineering,” a term that turns out to be older than the AI boom but brand new to prompting. The concept itself traces back to old-school flowchart thinking and dependency graphs used in software architecture, long before anyone was typing prompts into a chat box. No existing tool covered that specific angle for AI prompting, so the creator built one and called it Nodalo. It is a solo project, built out of genuine frustration rather than a funded startup trying to check a box on a roadmap, and that shows in how narrow and specific the tool actually is.
Here is the twist that actually got my attention. Nodalo is not just a pretty canvas for arranging boxes and arrows, plenty of those already exist, from Miro boards to n8n’s node editor to a dozen half-finished GitHub side projects. Every node carries what the creator calls a “node contract,” a tight, specific definition of what that step should do, with room to attach documents directly to it. Think of it like writing a tiny spec for each piece of your task instead of one giant paragraph trying to hold five requirements at once. Once the graph is built, you hand the whole structured thing (contracts, attachments, and all) straight to your AI agent, and it builds from that instead of your best guess at a paragraph. Instead of writing a normal prompt, forgetting half your requirements along the way, and rewording the same instruction five times, you draw the prompt once and let the agent read the map. If you have ever tried to prompt an agent to build a multi-step app and watched it drop a requirement from step three by the time it reaches step six, this is aimed squarely at that failure mode.
Here is the mini-workflow the post lays out, plus how I’d run it:
- 🧩 Open a workspace and drop in your first node for whatever the AI needs to build. Treat this like the first box on a whiteboard, not the whole plan at once.
- 📝 Fill out that node’s contract: the specifics, the constraints, the exact outcome you want. This is the step people will be tempted to rush, and it is the one that actually matters most.
- 📎 Attach any reference docs the node needs, right there on the node itself, so context lives next to the instruction instead of scattered across five browser tabs.
- 🔗 Chain your nodes together until the graph reflects the full workflow, start to finish, the same way you’d storyboard a video before shooting it.
- 🤖 Hand the completed graph to your AI agent and let it execute from the structure instead of a prompt, then check the output against each contract individually rather than judging the whole thing at once.
Pro tip: don’t skip the node contracts to save time. The whole value of this approach over a normal prompt is that details stop getting lost, and a half-filled contract just reintroduces the same vagueness you were trying to escape. If you find yourself writing “make it good” in a contract field, that is a sign you have not actually decided what you want yet, and no graph will fix that for you.
Pro tip two: if you’re not sure how the hand-off to your agent actually behaves, start with a small two-or-three-node graph before you build anything ambitious. Something as simple as “write a function, test the function, document the function” is enough to see how contracts translate into actual output. One commenter flagged that node-based prompt builders show up constantly and the real test is whether the auto-generation holds up under real use, and a second asked for a walkthrough because the site alone doesn’t make it obvious how nodes translate into an actual AI hand-off. Worth keeping in mind before you build your first big graph, and worth testing on something low-stakes before you trust it with a real project.
Nodalo is free to try, and the creator is actively answering questions in the thread, so if your prompts keep growing messier every time you touch them, go build one graph and see what your agent does with it. Swing by the original Reddit thread for the full back-and-forth, including that request for a clearer usecase walkthrough
Frequently Asked Questions
Q: What’s the learning curve like if I’ve been writing traditional prompts?
If you’re used to writing detailed prompts, you’re already thinking in the right way, just visually instead. Since you define what each node needs upfront, the AI’s got way more context than it would from text alone. Most people find visualizing workflows easier than describing them, so the transition should feel pretty natural.
Q: Does the auto-generation actually work, or do you end up fighting the AI like other tools?
The key difference is you’re giving the AI a lot more structure to work with. By defining node contracts and attaching documents upfront, you’re not leaving it guessing. That said, results depend on how well you define your setup, it’s not magic. Best move: try the free version and see how it goes for your use case.
Q: How does the handoff work? What happens in Nodalo vs. what the AI handles?
You build the workflow visually in Nodalo, set up nodes, define what each one needs, attach docs, wire everything up. Then you hand the structured graph to an AI agent, which reads it and generates the full workflow. So Nodalo handles the blueprint, and the AI fills in the execution details.
Q: What can I actually use this for?
Anywhere you’d write a complex multi-step prompt: content pipelines, data extraction, research workflows, or anything with multiple linked steps and specific constraints. The visual approach helps you think through the flow more clearly than writing it all out in text.
Q: How is this different from other node-based workflow builders?
Each node has a “node contract”, specific requirements and constraints you define, plus you can attach documents directly to nodes. When the AI takes over, it’s got all the context needed to generate the whole workflow automatically. Most other tools require you to write long prompts; Nodalo lets the structure do the talking.
I reduced the complexity of prompting advanced systems with this tool
by u/Weak_Ad4875 in PromptEngineering