Imbue
We build AI that works for humans
510 followers
We build AI that works for humans
510 followers
Imbue develops tools that help people think, create, and build. We believe technology should be loyal to the user and aligned with human goals.
We share many of our tools openly because we believe progress in AI should be collaborative and developer-driven.
This is the 8th launch from Imbue. View more
Blueprint
Launching today
Coding agents guess too much. On ambiguous tasks, they rush to code or invent a plan that sounds right and misses what you actually wanted.
Blueprint reads your code, asks grounded questions that matter, and hands any agent a plan worth executing.
The hope is that Blueprint catches what you didn't think to think about. The result is a plan your agent can execute in one shot.
Free, open source, and available as agent skills or extensions in Cursor, Windsurf, VS Code.
Free
Launch Team / Built With
Imbue
This nails a problem I saw constantly as CTO scaling an engineering team from 15 to 120 people. The gap between "what the developer typed into the prompt" and "what they actually needed" was the single biggest source of wasted agent cycles. Junior engineers especially would fire off a vague prompt, get back 200 lines of plausible-looking code, and spend hours debugging something that was wrong from the first instruction. The insight that the back-and-forth questioning phase is more valuable than the final plan really resonates - it mirrors how the best senior engineers work. They spend 80% of their time clarifying the problem and 20% solving it. Blueprint essentially automates the "senior engineer asking the right questions" step. Curious whether you're seeing different question patterns emerge across codebases - like whether Blueprint asks fundamentally different clarifying questions for a microservices repo vs. a monolith.
when you're working solo, there's no senior engineer to push back on a vague task. you're both the person writing the prompt and the person who should have asked better questions before writing it. ide extensions make sense — wondering if jetbrains / webstorm support is on the roadmap, or is the vs code ecosystem the focus for now.
free, open source, and available in the editors people are already in rather than a new tool to learn is the right distribution bet for developer tooling. adoption usually dies at the signup screen.