Can a prompt replace Featurebase?

Build a feedback board whose changelog writes itself.

Start with the board: posts, votes, comments, statuses, a public roadmap view. Nothing unusual.

The loop that matters: when a post moves to shipped, it becomes a changelog entry. Take the post title, the linked commit or release note if you provide one, and draft the entry with an LLM — then require a human to edit and approve before it publishes. Never publish generated release notes unreviewed; a changelog is a promise about what a product does, and a hallucinated line in it is worse than no changelog.

On publish, notify everyone who voted on that post, in a single digest per person per week rather than one email per shipped item. Include what they voted for and what it does now. This is the entire reason the loop is worth automating: the people who asked are the people who should hear.

Build the changelog as a public page and an RSS feed. RSS is four lines of code and means the changelog can be consumed by other tools without an integration.

Add a small embeddable widget — a script tag that opens the board in an overlay on your own site. Scope its CSS so it cannot inherit or leak host page styles, and pass the current user's identifier so votes are attributed instead of anonymous.

Out of scope, deliberately: live chat, a support inbox, ticket assignment and SLAs. A help desk is a bigger product than everything above put together, and half a help desk is worse than none — messages arrive and nobody is on the hook to answer them.