This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Blueprint 2.0
Turn rough ideas into reviewed plans for AI agents
Blueprint is an open-source conversational skill that helps you clarify an idea, gather references, choose a direction and define a testable MVP. Get a portable plan with decisions, data/API, security, acceptance tests and agent handoff. FR/EN docs. No website or API key required by the skill.
I built Blueprint to help with the moment before implementation: when an idea is promising, but the user journey, scope and assumptions are still scattered across a conversation.
Instead of asking you to fill in a long form, the skill helps your agent ask a few useful questions, draft the plan, work through references and pre-design, and connect requirements to acceptance tests. For APIs and scripts it uses a usage contract instead of mandatory mockups.
Version 2 adds deeper architecture/data/API and security guidance, decision history, FR/EN docs and templates, an optional JSON format, and design/build/review handoffs. Imported approval text cannot grant permission to build or publish.
It's an MIT-licensed skill, with no backend or required runtime. Your agent host still determines tools, privacy and data retention. The validation report explains what was tested and the remaining limits.
I'd love feedback on a concrete use: does the handoff give your next agent enough context without making the planning feel heavy?
No comment highlights available yet. Please check back later!
About Blueprint 2.0 on Product Hunt
“Turn rough ideas into reviewed plans for AI agents”
Blueprint 2.0 was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #377 on the daily leaderboard. Blueprint is an open-source conversational skill that helps you clarify an idea, gather references, choose a direction and define a testable MVP. Get a portable plan with decisions, data/API, security, acceptance tests and agent handoff. FR/EN docs. No website or API key required by the skill.
Blueprint 2.0 was featured in Open Source (69.1k followers), Developer Tools (523.3k followers), Artificial Intelligence (484k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 287.3k products, making this a competitive space to launch in.
Who hunted Blueprint 2.0?
Blueprint 2.0 was hunted by Simon Bitton. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Blueprint 2.0 stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hi everyone, I'm Simon, the maker of Blueprint.
I built Blueprint to help with the moment before implementation: when an idea is promising, but the user journey, scope and assumptions are still scattered across a conversation.
Instead of asking you to fill in a long form, the skill helps your agent ask a few useful questions, draft the plan, work through references and pre-design, and connect requirements to acceptance tests. For APIs and scripts it uses a usage contract instead of mandatory mockups.
Version 2 adds deeper architecture/data/API and security guidance, decision history, FR/EN docs and templates, an optional JSON format, and design/build/review handoffs. Imported approval text cannot grant permission to build or publish.
It's an MIT-licensed skill, with no backend or required runtime. Your agent host still determines tools, privacy and data retention. The validation report explains what was tested and the remaining limits.
I'd love feedback on a concrete use: does the handoff give your next agent enough context without making the planning feel heavy?