Show HN: I built a wizard to turn ideas into AI coding agent-ready specs
Mood
excited
Sentiment
positive
Category
startup_launch
Key topics
Ai Coding Agents
Product Development
Technical Planning
Ai Tooling
Software Development
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.
Discussion Activity
Moderate engagementFirst comment
5h
Peak period
10
Hour 10
Avg / period
2.5
Based on 25 loaded comments
Key moments
- 01Story posted
Nov 22, 2025 at 4:02 PM EST
1d ago
Step 01 - 02First comment
Nov 22, 2025 at 8:45 PM EST
5h after posting
Step 02 - 03Peak activity
10 comments in Hour 10
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 24, 2025 at 1:56 AM EST
54m ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
(And then the implementation plan is fed to the same sort of AI that you were going to give the "idea" to in the first place.)
If doing this gives good results, then it shouldn't be necessary.
Most advances in tools I've used in the last two years are exactly this sort of "automate the steering and feedback loop that the prompt goes through" automated-fairly-boilerplate-sequencing of refinement of initial idea -> plan -> execution -> feedback.
I'm using AI a lot, in planning but I take close manual oversight on specs and development plan and still read all active path code (give AI a little but not too much leeway on testing, since sometimes they start writing test asserting true == true).
there's no need for an app like this anyway.
You want this as a series of prompts that handle the various stages.
I guess we should tell thousands of AI researchers to stop what they're doing right now since you're a single prompt away from solving the problem??
If you're looking for feedback, you could include a tiny section on the homepage about how to run the output docs. e.g. put them in a folder, point Claude Code/Codex to it and give it the prompt.
Thanks for building this!
> If you're looking for feedback, you could include a tiny section on the homepage about how to run the output docs. e.g. put them in a folder, point Claude Code/Codex to it and give it the prompt.
This is great feedback - I totally agree - going to add this asap
Now you are going to have one write out instructions for an AI?! I guess we know how the AI apocalypse gets started!
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.