ideation-gauntlet

Generates differentiated hackathon ideas through consensus banning, evidence-grounded divergence, and judge simulation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/vinodkrishna221/Q-Trace --skill ideation-gauntlet-vinodkrishna221
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ideation-gauntlet
Source: https://github.com/vinodkrishna221/Q-Trace/tree/main/.agents/skills/ideation-gauntlet
Command: npx skills add https://github.com/vinodkrishna221/Q-Trace --skill ideation-gauntlet-vinodkrishna221

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hackathon teams routinely converge on the same obvious ideas, pick concepts they cannot build in the timebox, or choose projects that score poorly on the actual judging rubric. This Skill replaces unstructured brainstorming with a timed, evidence-driven procedure that produces a differentiated, buildable, rubric-aligned idea. ## Core Features & Use Cases - Consensus Banning: Simulates the average team's brainstorm, lists 12-15 predictable ideas, and bans them so divergence rounds cannot regress to consensus. - Evidence-Grounded Divergence: Requires web research on user pain, usable APIs and datasets, and prior winners before any candidate idea is accepted; every candidate must cite a verified finding. - Feasibility and Judge Simulation: Scores survivors on demo-impact versus build-cost, runs a deployability battery (rails, operator, zero-training, cold-start, unit economics, zero-bars), and outputs a ranked IDEA-BRIEF. - Use Case: A four-person team at a 36-hour sponsor-judged hackathon runs the gauntlet in 90 minutes, kills the obvious chatbot ideas, and commits to an offline-first IVR solution with a verified delivery rail and a sponsor-prize portfolio. ## Quick Start Run the ideation gauntlet on this hackathon problem statement and judging criteria to produce an IDEA-BRIEF with a ranked shortlist of buildable ideas.

Frequently Asked Questions about ideation-gauntlet

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

FAQPage Schema
How do I come up with a unique hackathon idea?

Run a structured gauntlet: first simulate and ban the 12-15 obvious ideas other teams will pitch, then generate candidates through divergence lenses like no-UI delivery, domain collision, and constraint flips. Every candidate must cite a verified research finding to survive.

How to evaluate hackathon ideas against judging criteria?

Extract the rubric into a weights table, then score each surviving idea per criterion from 1-10 with a sponsor-fit bonus. Unpublished rubrics default to an assumed 25/25/25/25 split across innovation, technical, impact, and presentation.

How long should hackathon ideation take?

The full gauntlet is timeboxed to 60-90 minutes across seven steps, from problem-statement interrogation to final decision. An idea chosen at hour five loses to a worse idea chosen at hour one because build time dominates outcomes.

Should I avoid obvious ideas at hackathons?

Obvious ideas are banned at innovation-scored events, but at sponsor-judged events a well-executed obvious idea can win. The recommended synthesis is to keep the obvious idea's clarity while differentiating its delivery through lenses like offline-first or agent-native design.

What makes a hackathon project deployable rather than just a demo?

A deployability battery scores six tests: riding existing delivery rails, having a real operator, first use under two minutes, no cold-start data dependency, sourced unit economics, and functioning at zero connectivity. Failures cap the impact score and enter the risk register.