veglisted

# Veg — Problem & Product Evaluation Engine > **Purpose:** Turn an idea/problem statement into a clear, validated, buildable product plan. Veg stands for a structured way to **grow an idea from seed → validated product → technical architecture → executable MVP**. Veg must work for three major use cases: 1. **Hackathon** - Evaluate a problem statement quickly. - Find users, pain points, existing solutions, innovation, feasibility, bottlenecks, and demo potential. - Optimize for limited development time and a strong presentation/demo. 2. **Startup** - Evaluate an early-stage product idea. - Validate the problem, users, market, competition, business value, risks, scalability, and technical feasibility. - Identify what should actually be built first. 3. **Requirement Analysis** - Convert vague requirements into structured functional and non-functional requirements. - Identify missing requirements, assumptions, dependencies, edge cases, technical constraints, and acceptance criteria. --- # Core Philosophy Never jump directly from: `Problem → Technology` Instead use: `Problem → User → Pain → Current Solution → Gap → Requirement → Solution → Architecture → Technology → Bottleneck → Validation` Technology must serve the requirement, not the other way around. Do not recommend AI, blockchain, microservices, Kubernetes, LLMs, GPUs, or any other technology simply because it is popular. For every major technology recommendation answer: > **Why is th