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).
Spec-driven development has the right idea and the wrong timing. Every tool out there - Spec Kit, Kiro, the rest - puts spec-writing in front of one engineer, at the keyboard, right as they're about to build. Penling flips this approach and uses generative AI from the start of your project all the way through the lifecycle to a reviewable PR containing tested work and a fully documented build specification that your whole team agreed on.
My day job is at a large tech company. Hundreds of engineering teams, and every one of them is somewhere different on AI adoption. Some are still treating coding agents as a curiosity. Some have quietly rebuilt their whole workflow around them. Most are in the messy middle, and watching that middle is where the idea for Penling came from.
Spec-driven development has arrived, and I think it's the right idea. Tools like SpecKit and Kiro put the specification front and center to the coding workflow, and the results are noticeably better - an agent working from a written spec produces dramatically better output than an agent working from a vibe and a prompt.
But look at where the spec gets written. In the engineer's IDE. In the terminal. At the moment the task gets picked up.
That's a long way from where the product decisions were actually made.
I built Penling as the answer to how we can produce better outcomes by shifting the thinking that goes into a specification beyond the engineer in the seat, making it a team artefact and a single source of truth (no more confluence -> Jira -> specification hopping).
At the moment it works only with Github as the connected VCS. But the LLM integration is solid and really helps guide users to producing faster project goals, focused work, MCP available tasks that you use with your own LLM (Claude, Codex etc) and ultimately a reviewable and spec file.
Give it a go. I'd love any and all feedback. I'm introducing Penling to a team at my day job company soon so keep an eye out for improvements as we learn more about how it performs on a day-to-day basis.
Cheers,
Paul 👋
No comment highlights available yet. Please check back later!
About Penling on Product Hunt
“Spec-driven-development for product teams”
Penling was submitted on Product Hunt and earned 4 upvotes and 1 comments, placing #160 on the daily leaderboard. Spec-driven development has the right idea and the wrong timing. Every tool out there - Spec Kit, Kiro, the rest - puts spec-writing in front of one engineer, at the keyboard, right as they're about to build. Penling flips this approach and uses generative AI from the start of your project all the way through the lifecycle to a reviewable PR containing tested work and a fully documented build specification that your whole team agreed on.
Penling was featured in Productivity (654.5k followers), Software Engineering (42.6k followers) and Artificial Intelligence (471.7k followers) on Product Hunt. Together, these topics include over 250.1k products, making this a competitive space to launch in.
Who hunted Penling?
Penling was hunted by Paul Schneider. 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 Penling stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Paul Schneider