validate-idea

Validates product ideas through five sequential questions and returns a keep or kill verdict.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill validate-idea-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-idea
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/validate-idea
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill validate-idea-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Early-stage idea backlogs fill up with concepts that were never pressure-tested, wasting time on full discovery sessions for ideas that should have been cut immediately. This Skill applies a fast five-question filter so weak ideas are killed before committing to a full grilling session. ## Core Features & Use Cases - Five-Question Filter: Asks who has the problem, how they solve it today, what metric improves, why your team is the right one, and what the smallest shippable slice is — one question at a time. - Keep or Kill Verdict: Synthesizes all five answers into a bolded verdict with a one-sentence reason, flagging vague, unmeasurable, or indefensible answers. - Guided Probing: Issues at most one follow-up probe per question when answers are weak, then captures the answer as-is for the verdict. - Use Case: You have a line in docs/ideas-backlog.md for a client-invoicing tool. Run the filter, answer the five questions, and get a keep verdict that routes you to the full grill — or a kill verdict with a sharpening criterion for revisiting later. ## Quick Start Ask the assistant to validate the idea "automated invoice reminders for freelance designers" using the five-question filter.

Frequently Asked Questions about validate-idea

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

FAQPage Schema
How do I validate a product idea before building it?▼

Validate a product idea by answering five questions: who has the problem, how they solve it today, what metric improves, why your team is right for it, and what the smallest shippable slice is. Concrete, measurable answers indicate a keep; vague answers indicate a kill.

What questions should I ask to filter weak startup ideas?▼

Ask about the specific user with the problem, their current workaround or competitor, the single measurable metric that improves, your defensible advantage, and the smallest testable slice shippable in one to two days. Two or more weak answers means the idea should be killed.

When should I kill an idea instead of pursuing it?▼

Kill an idea when two or more of the five validation answers are weak, unmeasurable, or unanswerable — for example, no specific target user, no measurable metric, or no defensible angle. A kill verdict is recoverable and means revisit later with sharper answers.

Does idea validation require market or competitor research?▼

No external research is required. The current-solution question relies on your own observation of alternatives, competitors, or manual workarounds. The filter is a judgement call based on your answers, not a web-crawled competitive analysis.

What happens after an idea passes the validation filter?▼

A keep verdict routes the idea to a full grilling session that pressure-tests it before any spec or PRD work begins. Validation is the front-door gate, not a replacement for deeper discovery.