[HN Gopher] Show HN: I built a wizard to turn ideas into AI codi...
___________________________________________________________________
Show HN: I built a wizard to turn ideas into AI coding agent-ready
specs
I created vibescaffold.dev. It is a wizard-style AI tool that will
guide you from idea - vision - tech spec - implementation plan. It
will generate all the documents necessary for AI coding agents to
understand & iteratively execute on your vision. How it works: -
Step 1: Define your product vision and MVP - Step 2: AI helps
create technical architecture and data models - Step 3: Generate a
staged development plan - Step 4: Create an AGENTS.md for automated
workflows I've used AI coding tools for awhile. Before this
workflow (and now, this tool), I kept getting "close but not quite"
results from AI coding tools. I learned that the more context &
guidance I gave these tools up front, the better results I got.
The other thing I have found with most tools that attempt to
improve on "vibe coding" is that they add abstraction. To me, this
just adds to the problem. AI coding agents are valuable, but they
are error-prone - you need to be an active participation in their
work. This workflow is designed to provide a scaffolding for these
AI agents, while minimizing additional abstraction. Would love
feedback on the workflow - especially curious if others find the
upfront planning helpful or constraining.
Author : straydusk
Score : 9 points
Date : 2025-11-22 21:02 UTC (1 hours ago)
(HTM) web link (vibescaffold.dev)
(TXT) w3m dump (vibescaffold.dev)
| esafak wrote:
| You can already do this in your coding agent ? You just need the
| LLM to index the code base, and the rest is easy. I need a
| before-and-after to understand what you are doing differently.
| straydusk wrote:
| Maybe that's something I should add, to more clearly illustrate
| it. This tool is creating a spec that the AI coding agent of
| your choice can execute on, it's not an AI coding itself. Or
| maybe I'm not sure what you're getting at?
| Avicebron wrote:
| I'm not sure if it's intended behavior or not, but after it
| generated the spec it did offer to write the code and then
| generated it
| esafak wrote:
| I mean I can already iterate on a spec with the agent; I do
| not need a separate tool.
___________________________________________________________________
(page generated 2025-11-22 23:00 UTC)