hackathon-problem-first

Identify real-world pain points and trends to seed hackathon concepts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fabianferno/skills --skill hackathon-problem-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hackathon-problem-first
Source: https://github.com/fabianferno/skills/tree/main/skills/hackathon-problem-first
Command: npx skills add https://github.com/fabianferno/skills --skill hackathon-problem-first

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides teams to ideate hackathon concepts by starting from real-world problems and credible trends, rather than chasing sponsor-driven prizes, ensuring the narrative remains user- and product-focused.

Core Features & Use Cases

  • Problem-first workflow: Spot credible pains and trends, then outline a narrow MVP that addresses a real user need.
  • Prize mapping last: Once the product story is solid, map relevant sponsor tracks or prizes to demonstrate alignment.
  • Reference-driven ideation: Leverage example projects and prompts to accelerate brainstorming and maintain narrative quality.
  • Handoff to implementation: Use structured templates and checklists to transition from ideation to execution, including UX refinement and pitch readiness.
  • Scalable prompts: Use anchor prompts to generate one-line anchors, product definitions, and user journeys that can be reused across teams.

Quick Start

Spot a credible real-world problem, define a narrow MVP that delivers tangible value, articulate the user job and UX, then assess prize alignment only after the product concept is clear.

Frequently Asked Questions about hackathon-problem-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I brainstorm hackathon ideas from real problems instead of sponsor tracks?

To brainstorm hackathon ideas from real problems, you identify real-world pain points and credible trends first, then outline a narrow MVP that addresses a tangible user need before mapping to sponsor prizes.

What is the problem-first workflow for hackathon ideation?

The problem-first workflow for hackathon ideation is a process of spotting credible pains, defining a narrow MVP, articulating user jobs and UX, and assessing prize alignment only after the product concept is solid.

How do I scope a hackathon MVP that judges and users understand?

To scope a hackathon MVP that judges and users understand, you apply the problem-first workflow across product scoping and UX polish, generating one-line anchors, product definitions, and user journeys.

When should I map sponsor prizes during hackathon pitch preparation?

You should map sponsor prizes during hackathon pitch preparation only after your product story is solid, ensuring the narrative remains user- and product-focused while demonstrating prize alignment.

Can I use reference templates to transition from hackathon ideation to execution?

Yes, you can use structured templates and checklists to transition from hackathon ideation to execution, covering UX refinement and pitch readiness to support team collaboration and evaluation.

Does hackathon problem-first ideation work for team collaboration?

Yes, hackathon problem-first ideation works for team collaboration by encapsulating the process, references, and handoffs in structured templates and scalable prompts that can be reused across teams.