rt-graham

Guide founders to validate startup ideas through user demand and PMF checks.

28|11|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/risingdream/roundtable --skill rt-graham
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rt-graham
Source: https://github.com/risingdream/roundtable/tree/main/skills/vc/rt-graham
Command: npx skills add https://github.com/risingdream/roundtable --skill rt-graham

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps early-stage founders pressure-test startup ideas by diagnosing whether they’re building something people actually want, and by turning “vague market talk” into user-centered validation.

Core Features & Use Cases

  • User demand + PMF check: Evaluates whether users would be upset if the product disappeared, clarifying the gap between assumptions and evidence.
  • Actionable startup strategy: Turns hesitation and “too hard” problems into concrete next steps (identify the schlep, talk to users, iterate).
  • Founder decision-making frameworks: Applies “default alive vs. default dead,” relentless resourcefulness, and “do things that don’t scale” to guide what to do next.
  • Use Case: You have a product idea and suspect it’s promising, but you don’t know if anyone would actually want it enough to pay—this skill helps you design the user conversations and iteration path that reveal PMF (or the lack of it).

Quick Start

Ask for a Paul Graham-style validation plan in Korean for your idea, including who the users are, what to ask them, what evidence would count as PMF, and what the next iteration should be.

Frequently Asked Questions about rt-graham

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

FAQPage Schema
How do I validate my startup idea and test if users actually want the product?

Startup validation requires testing whether users actually want the product by designing targeted user discovery conversations, applying explicit PMF criteria, and iterating based on whether users would be upset if the product disappeared.

What questions should I ask during user discovery interviews for product validation?

User discovery conversations should focus on identifying the schlep, testing whether users would pay, and gathering evidence that counts as product-market fit rather than relying on vague market assumptions or hypothetical interest.

What startup strategy frameworks help founders decide what to do next when validation evidence is unclear?

Founder decision-making frameworks like default alive vs. default dead, relentless resourcefulness, and do things that don't scale guide what to do next by turning hesitation and unclear evidence into concrete iteration steps.

When should I pivot or iterate my startup based on user feedback?

Pivot or iterate when user discovery conversations reveal a gap between your assumptions and evidence, using schlep navigation to identify the real problem and talk-to-users discipline to design the next product iteration.

Can I use this approach for early-stage startup idea selection before building anything?

Early-stage idea selection benefits from user-focused reasoning and startup heuristics that pressure-test whether you are building something people want, turning vague market talk into a concrete validation plan before development.