Blueprint - One-shot bigger coding tasks
by•
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.
Replies
Imbue
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.
Imbue
@webappski Exactly, our goal is for blueprint to catch stuff you didn't think to think about when working solo and to take on some of the burden of thinking through all the details alone. We're open to releasing the extension for other IDEs if there's enough interest!
Imbue
@webappski It's great that Blueprint can be run outside of the agent loop, almost like a "neutral" or "third-party" planner to help gut check the work your conjuring up. Give it a try and let us know how it works for you!
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.
Imbue
@dmitry_isaevski If you like free and open-source, then you'll love Imbue's suite of developer tooling: https://github.com/imbue-ai We're on a mission to make open agent platforms accessible for all.
Imbue
Nayana, it was wonderful iterating to simplify and refine the IDE plugin together, congrats on the launch!
Imbue
@thisisehsan 🙏
Imbue
@thisisehsan Appreciated your expertise! It was great to see it come together over time!
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.
Imbue
@avrisimon Glad to hear you resonate with our vision! We've noticed for smaller projects and tasks it primarily asks questions about the scope and behavior of your task. For larger mature codebases Blueprint questions also pay attention to things like existing patterns in the codebase and points of integration with the existing code.
Imbue
@avrisimon "Measure twice, cut once" —Blueprint 😆