RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), and GitHub. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[OpenSpec] Reverse-engineer specs from existing implementations (code-first workflow)

Provide a mechanism to generate specs and documentation retroactively from existing code. This would support teams who prefer a code-first workflow, allowing them to create OpenSpec artifacts after manual implementation.

Original Source

@@alfred-openspec | 3 pts | 2/18/2026

## Problem Teams adopting OpenSpec often have members who prefer implementing features manually with minimal AI assistance. After implementation, they need a way to generate specs and documentation retroactively from the existing code. Currently, OpenSpec is optimized for a spec-first workflow. There is no native support for generating specs from already-implemented code. ## User Story > "I have a specific use case: for team members who prefer to implement features manually with minimal AI assistance, is it possible to generate the specifications and documentation after the code is written? Specifically, can `/opsx:verify` be used to 'reverse-engineer' these artifacts then archive it?" > > "In your experience, do you recommend generating specs for manual implementations, or is the tool optimized for a 'spec-first' workflow?" > > — Ousama Esbel (Discord, rolling out to a 15-person team) ## Context - Team of 15 members with mixed workflows (some AI-assisted, some manual coding) - N

Discussion

Loading comments...