problem-discovery

Turns fuzzy hypotheses into falsifiable Frames using freelance marketplace data.

27|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/Code-My-Spec/market_my_spec --skill problem-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: problem-discovery
Source: https://github.com/Code-My-Spec/market_my_spec/tree/main/priv/skills/problem-discovery
Command: npx skills add https://github.com/Code-My-Spec/market_my_spec --skill problem-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Takes fuzzy founder hypotheses and turns them into falsifiable Frames backed by money signals, guiding a 6-step problem-discovery flow from Frame to Board.

Core Features & Use Cases

  • Frame creation: define a problem hypothesis with saved searches, money_gate, and a kill_condition.
  • End-to-end discovery: automatically run Gather, Cluster, Score, Red-team, and Board steps to surface killable problem leads.
  • Decision support: produce a structured Board with kill arguments to drive early customer conversations.
  • Use Case: validate a market hypothesis using Upwork postings to show where money already moves.

Quick Start

Provide a fuzzy hypothesis, convert it into a Frame, then run the full discovery flow to produce a Board for review.

Frequently Asked Questions about problem-discovery

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

FAQPage Schema
How do I validate a startup idea using freelance marketplace spending data?

You can validate product opportunities by converting a fuzzy hypothesis into a falsifiable Frame backed by observed freelance marketplace spending. The system requires saved searches, a money_gate, and a kill_condition to execute the discovery flow.

What is a money_gate in problem discovery and why do I need it?

A money_gate is a required threshold in problem discovery that confirms real financial spending exists for a hypothesis. It acts as objective evidence that money already moves around the problem before you invest in building a solution.

How do I run a formal problem-discovery flow to test a market hypothesis?

Run a formal problem-discovery flow by defining a Frame, then automatically executing Gather, Cluster, Score, Red-team, and Board steps. This structured process surfaces killable leads and produces arguments to guide early customer conversations.

Can I use Upwork postings to check if customers are already paying to solve a problem?

Yes, you can use Upwork postings to validate where money already moves by setting up saved searches within a Frame. The gathered data is clustered and scored to determine if observed marketplace spending justifies pursuing the opportunity.

What is the best way to red-team a product hypothesis before committing to development?

The best way to red-team a product hypothesis is to run an automated discovery flow that includes a dedicated Red-team step. This challenges your initial assumptions and generates kill arguments to prevent pursuing unvalidated opportunities.

When should I use a kill_condition during market validation?

You should define a kill_condition during market validation to establish clear criteria for abandoning a problem hypothesis. It works alongside the money_gate to ensure you only pursue product opportunities that pass falsifiable financial checks.