Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
| Date | Stars |
|---|---|
| 2026-07-31 | 1764 |
| 2026-08-06 | 1764 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Claude Requirements Gathering System An intelligent requirements gathering system for Claude Code that progressively builds context through automated discovery, asks simple yes/no questions, and generates comprehensive requirements documentation. ## 🎯 Overview This system transforms the requirements gathering process by: - **Codebase-Aware Questions**: AI analyzes your code first, then asks informed questions - **Simple Yes/No Format**: All questions are yes/no with smart defaults - just say "idk" to use defaults - **Two-Phase Questioning**: 5 high-level questions for context, then 5 expert questions after code analysis - **Automated Documentation**: Generates comprehensive specs with specific file paths and patterns - **Product Manager Friendly**: No code knowledge required to answer questions ## 🚀 Quick Start ```bash # Start gathering requirements for a new feature /requirements-start add user profile picture upload # Check progress and continue /requirements-status # View current requirement details /requirements-current # List all requirements /requirements-list # End current requirement gathering /requirements-end # Quick reminder if AI strays off course /remind ``` ## 📁 Repository Structure ``` claude-requirements/ ├── commands/ # Claude command definitions │ ├── requirements-start.md # Begin new requirement │ ├── requirements-status.md # Check progress (alias: current) │ ├── requirements-current.md # View active requirement │ ├── requirements-end.md # Finalize requirement │ ├── requirements-list.md # List all requirements │ └── requirements-remind.md # Remind AI of rules │ ├── requirements/ # Requirement documentation storage │ ├── .current-requirement # Tracks active requirement │ ├── index.md # Summary of all requirements │ └── YYYY-MM-DD-HHMM-name/ # Individual requirement folders │ ├── metadata.json # Status and progress tracking │ ├── 00-initial-request.md # User's original request │ ├── 01-discovery-questions.md # 5 context questions │ ├── 02-discovery-answers.md # User's answers │ ├── 03-context-findings.md # AI's code analysis │ ├── 04-detail-questions.md # 5 expert questions │ ├── 05-detail-answers.md # User's detailed answers │ └── 06-requirements-spec.md # Final requirements │ └── examples/ # Example requirements ``` ## 🔄 How It Works ### Phase 1: Initial Setup & Codebase Analysis ``` User: /requirements-start add export functionality to reports ``` AI analyzes the entire codebase structure to understand the architecture, tech stack, and patterns. ### Phase 2: Context Discovery Questions The AI asks 5 yes/no questions to understand the problem space: ``` Q1: Will users interact with this feature through a visual interface? (Default if unknown: YES - most features have UI components) User: yes Q2: Does this feature need to work on mobile devices? (Default if unknown: YES - mobile-first is standard) User: idk AI: ✓ Using default: YES [Continues through all 5 questions before recording answers] ``` ### Phase 3: Targeted Context Gathering (Autonomous) AI autonomously: - Searches for specific files based on discovery answers - Reads relevant code sections - Analyzes similar features in detail - Documents technical constraints and patterns ### Phase 4: Expert Requirements Questions With deep context, asks 5 detailed yes/no questions: ``` Q1: Should we use the existing ExportService at services/ExportService.ts? (Default if unknown: YES - maintains architectural consistency) User: yes Q2: Will PDF exports need custom formatting beyond the standard template? (Default if unknown: NO - standard template covers most use cases) User: no [Continues through all 5 questions before recording answers] ``` ### Phase 5: Requirements Documentation Generates comprehensive spec with: - Problem statement and solutio
Excerpt of 8,450 characters
Read on GitHub
4
Would you bet a product on this? Bounded 0–100 and slow moving.
Not classified yet. Classification runs as part of npm run ingest.
