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] Allow custom spec schemas and formats

Remove hardcoded spec structure expectations (e.g., `## Requirements`, `### Requirement:`) in parsers, validators, and generators. This would enable support for custom schemas and different spec formats (e.g., `## Functional Requirements`, scenarios in separate files) without validation failures.

Original Source

@@lsmonki | 4 pts | 2/5/2026

## Problem OpenSpec hardcodes spec structure expectations (## Requirements, ### Requirement:, #### Scenario: inline) throughout parsers, validators, and generators. This means custom schemas that define different formats (e.g., ## Functional Requirements, scenarios in separate verify.md files) fail validation even when their specs are correctly structured according to their own schema. This prevents OpenSpec from working with projects that have pre-existing specs in different formats. Real-world scenarios include: - Teams with specs created before adopting OpenSpec - Specs generated by other tools - Human-written specs following company/team conventions - Custom schemas that use different headers (e.g., `## Functional Requirements`) or separate verification files OpenSpec should adapt to existing spec formats, not impose it

Discussion

Loading comments...