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] Numbered artifact files and browser UI for exploration

Implement numbered artifact filenames (zero-padded sequence numbers) for chronological sorting and unambiguous referencing. Additionally, provide a lightweight tool (CLI or web UI) to browse these artifacts, inspired by MADR.

Original Source

@@Xavier-Brinon | 1 pts | 2/18/2026

# Feature Request: Numbered Artifact Files + Browser UI I'd like to keep a chronological order when exploring artifacts. ## Summary Two related improvements inspired by [MADR](https://github.com/adr/madr) (Markdown Architectural Decision Records): 1. **Numbered artifact filenames** — prefix every change artifact with a zero-padded sequence number so artifacts sort chronologically and can be referenced unambiguously by number. 2. **Artifact browser** — a lightweight tool (CLI or web UI) to list, filter, and read all artifacts across changes, similar to what [Log4brains](https://github.com/thomvaill/log4brains) or [adr-viewer](https://github.com/mrwilson/adr-viewer) do for ADRs. --- ## Motivation ### Problem 1 — artifacts have no stable, ordered identity Today a completed change lives at `openspec/changes/archive/YYYY-MM-DD-<name>/`. Inside it, artifact files are named by role (`proposal.md`, `design.md`, `tasks.md`) but carry no global sequence number. This means:

Discussion

Loading comments...