gstack-office-hours

Apply Garry Tan's GStack office-hours questions to validate product ideas.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/mick-net/Skills --skill gstack-office-hours-mick-net
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-office-hours
Source: https://github.com/mick-net/Skills/tree/main/gstack-office-hours
Command: npx skills add https://github.com/mick-net/Skills --skill gstack-office-hours-mick-net

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you validate product, feature, or startup ideas by applying a structured, YC-style question set that challenges the reality and viability of your concept.

Core Features & Use Cases

  • Idea Validation: Apply a series of forcing questions to pressure-test the demand, status quo, and viability of your idea.
  • Contextual Analysis: Leverages the company's context within a repository to tailor the questions and insights.
  • Decision Making: Provides a framework to make informed decisions on whether to build, validate first, or pivot your idea.

Quick Start

Use the gstack-office-hours skill to pressure-test your product idea 'New Social Media App'.

Frequently Asked Questions about gstack-office-hours

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

FAQPage Schema
How do I validate a startup idea before building the product?

Idea validation involves pressure-testing demand reality, status quo alternatives, and the narrowest paid wedge to challenge your concept's viability. This YC-style framework applies structured forcing questions to determine whether to build, validate first, or pivot your product or startup concept.

What is the best way to test product demand for a new feature concept?

Testing product demand requires assessing observable user behavior and desperate specificity rather than just asking what users want. This validation workflow applies forcing questions to evaluate if the problem is real and whether users will actually pay for your narrowest viable wedge.

Can I use YC-style validation questions for business planning within an existing company?

Yes, you can use YC-style validation questions for business planning within an existing company. The workflow leverages your company context within a repository to tailor questions for product, feature, and startup concepts, applying evidence-based decision-making to your specific environment.

How do I make evidence-based decisions on whether to build or pivot my product?

Evidence-based decision-making for building or pivoting requires evaluating demand reality and performing risk-based assessments on your idea. This framework applies forcing questions to pressure-test your concept, providing a structured decision on whether to proceed with building or pivot.

What are the limitations of using forcing questions for idea validation?

The limitation of using forcing questions for idea validation is that the framework requires deep contextual awareness and honest risk-based assessment to be effective. Without accurate company context and observable user behavior data, the resulting decision to build or pivot may lack sufficient evidence.